Abstract: Embodiments described herein provide an attention-based tree encoding mechanism. Specifically, the attention layer receives as input the pre-parsed constituency tree of a sentence and the lower-layer representations of all nodes. The attention layer then performs upward accumulation to encode the tree structure from leaves to the root in a bottom-up fashion. Afterwards, weighted aggregation is used to compute the final representations of non-terminal nodes.

Abstract: Disclosed herein are system, method, and computer program product embodiments providing a data sorting and rating system. An embodiment operates by detecting a user modification of a particular value of a sorted plurality of values of a column displayed in a visual interface including a sorting visual indicator indicating that the plurality of values are sorted. It is determined that the values are no longer sorted after the user modification. The sorting visual indicator is replaced with a refresh visual indicator based on the determination that the plurality of values are no longer sorted. The values including the user modification are re-sorted based on a selection of the refresh visual indicator. The re-sorted plurality of values including the user modification of the particular value are provided for display in the visual interface.

Abstract: In accordance with embodiments, there are provided techniques for managing functionality changes of a database platform of a service provider. The techniques facilitate implementing changes to the database platform while minimizing work flow reductions to users of the database platform. To that end, one embodiment of the present invention delays implementation of the changes for a duration of time to provide users of the database platform an opportunity to adjust behavioral interaction with the database platform. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the users may be afforded an opportunity to selectively enable and disable the functionality changes before the duration of time expires.

Abstract: Approaches for multitask learning as question answering include an input layer for encoding a context and a question, a self-attention based transformer including an encoder and a decoder, a first bi-directional long-term short-term memory (biLSTM) for further encoding an output of the encoder, a long-term short-term memory (LSTM) for generating a context-adjusted hidden state from the output of the decoder and a hidden state, an attention network for generating first attention weights based on an output of the first biLSTM and an output of the LSTM, a vocabulary layer for generating a distribution over a vocabulary, a context layer for generating a distribution over the context, and a switch for generating a weighting between the distributions over the vocabulary and the context, generating a composite distribution based on the weighting, and selecting a word of an answer using the composite distribution.

Abstract: Techniques and systems for completing a database query. A time to complete a synchronous query in response to receiving an original database query is estimated by a database management system provided by one or more computing devices. A synchronous database query corresponding to the original database query is performed with the database management system if the estimated time to complete the synchronous query is less than a pre-selected threshold time. One or more asynchronous queries corresponding to the original database query are performed with the database management system if the estimated time to complete the synchronous query is greater than the pre-selected threshold time. A result, whether from a synchronous query or one or more asynchronous queries, is stored in an object within a non-relational database system.

Abstract: Disclosed herein are system, method, and computer program product embodiments for self-paced migration of an application programming language (API) gateway. An embodiment operates by receiving a functional test suite corresponding to an application programming interface (API). The embodiment generates a knowledge graph of information by combining a test result graph of information based on a result of execution of one or more tests in the functional test suite with a metadata linked graph of information based on metadata corresponding to the one or more APIs. The embodiment then generates an alert message corresponding to the function test suite based on the knowledge graph of information.

Abstract: Disclosed herein are system, method, and computer program product embodiments for implementing automatic taxonomy tags in an API microgateway. The API microgateway may receive a plurality of API requests for an API managed by a customer in a period of time and route the plurality of API request to an instance of the API according to a policy of the API. The API microgateway may aggregate metrics information related to the plurality of API requests. The aggregated metrics information may include request features, response features, policy features, and performance features. In response to a cluster of the metrics information corresponding to a tag in a tag prediction system, the aggregated metrics information may be labeled with the tag. The tag and the aggregated metrics information may be added to an access log and sent to the customer.

Abstract: Disclosed herein are system, method, and computer program product embodiments for providing a universal coding language and construct for an application programming language (API) environment. In the environment, a standard language with a predefined and universal format is used for each of the different internal code modules. A translator is then provided in order to translate the standard language to the proprietary language of specific gateways or other vendor products. In some embodiments, a parser is used to in order to convert the code modules to an internal model. The internal model allows a user to visualize or otherwise understand the configuration that has been coded, and to make any necessary modifications.

Abstract: Multiple systems, methods, and computer program product embodiments for password-less authentication using key agreement and multi-party computation (MPC). In one or more embodiments, following an authentication request received by a host computing device, the host computing device and a user computing device generate a shared key using a key agreement algorithm. Then, the host computing device generates a challenge that is encrypted using the shared key and transmitted to the user computing device. The user computing device decrypts the challenge after regenerating the shared key and sends the decrypted result to the host computing device as the challenge response. The authentication request is granted by the host computing device if the challenge and the challenge response match. New keys and a new challenge are generated for each authentication request. This process relies on public key cryptography eliminating the needs for passwords.

Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

Abstract: Disclosed herein are system, method, and computer program product embodiments for providing asynchronous backend processing of complex, time consuming, and/or expensive jobs. A command line interface (CLI) provides a command interface between a user and a backend processing server. The CLI sends a job request to the backend server, which immediately replies to the request with a confirmation message that includes a job identifier. This response is sufficient to allow the CLI to end its wait for the job response. Meanwhile, the backend server carries out the job by parsing the job into component tasks according to a declaration file and assigns those different tasks to different work servers. The backend server functions as a master server, tracking the statuses of the different tasks and assigning out new tasks until the job is complete. An overall job status is provided to the CLI upon request by referencing the job identifier.

Abstract: A computer-based system may be configured to collect metadata and/or the like indicative of all the metrics exposed from a data pipeline (e.g., an ETL pipeline, etc.) and transform the metrics into a single group of metrics user-facing, user-specific, user-configured, and/or the like metrics that allow the maturity and quality of data and/or data records to be analyzed and/or displayed. Collected metrics can be agnostic of a source data flow component of a data pipeline and/or resource technology (e.g., API, etc.). Collected metrics may indicate a measure of data freshness, data duplication, new data records, updated date data records, data errors, and/or the like.

Abstract: A computer-based system may be configured to collect metadata for each source and target defined for a data pipeline and formatting information (e.g., schemas, transformations, etc.) associated with each entity and field. During the definition of the pipeline, how the data will end up in the target may be defined, for example, by a user of the computer-based system via a GUI/interface and/or the like. Information (e.g., modification information, etc.) describing how the data will end up in the target may be defined, stored, and accessed to determine and/or track over which fields and entities are affected by the user-defined mutations and over which schemas. Lineage information (e.g., a genealogical tree, data lineage tracing, etc.) describing a data, version, and transformation may be generated and used to determine a source for a data record, how changes to the data record are related, how lineage evolved, and/or the like.

Abstract: Disclosed herein are system, method, and computer program product embodiments for automatically cataloging updated Application Programming Interface (API) specifications. The API specifications may have been previously published to an application exchange platform. An automatic cataloging tool installed at an API development system may identify an updated API specification committed to an API specification repository. To validate that a change has been made, the automatic cataloging tool may compare the updated specification, metadata, and/or referenced documentation files to an API specification previously posted to the application exchange platform. In response to determining that the API specifications differ, the automatic cataloging tool may transmit the updated API specification to the application exchange platform. The application exchange platform may then replace the previous API specification with the updated API specification for client devices to view.

Abstract: Disclosed herein are system, method, and computer program product embodiments for automatically discovering an API for publishing within a data repository. A discovery tool is used either on a server computer or a customer computer to examine the files stored in the data repository. A search of the repository is conducted to identify root API files that form the basis of an API. A first examination is conducted in which the files are examined for common indicia associated with known API standards. Then a second examination is done of the root API candidates found in the first examination to identify which of the root API candidates is actually a root API. Once the root API has been located, it is executed in a computer environment, and its dependents are detected. Once all the necessary API files have been located, they are packaged and automatically published.

Abstract: Disclosed herein are system, method, and device embodiments for a data bridge adapter in a data integration platform that models any application programming interface as an entity-relationship model. This technique allows an individual using an integration platform to map and transform the entity-relationship model without having to create any custom code. The user may specify target parameters as part of an ETL process, and the entity relationship model may allow appropriate data and API calls to be generated to pass the data to the specified target. By creating an entity-relationship model from any API, the technique further supports versioning, schema change resolution, compatibility detection and other features. Furthermore, data visualization software may use the entity-relationship model to allow users to explore and analyze the data represented in the entity-relationship model.

Abstract: Disclosed herein are system, method, and device embodiments for enriching the capabilities of an API management product by deploying an augmented circuit breaker policy at an API gateway to automate regression analysis. Based on the augmented circuit breaker policy, the API gateway may perform curative remedies when a triggering condition occurs, e.g. rolling back the software release or alerting administrators. In one use case, the augmented circuit break policy may mitigate the damage of a faulty software release by programmatically directing all requests received at the API gateway to a stable version of the API. The benefits may be extended by using machine learning to train normality models on the typical behavior of a particular API. A user may then configure an augmented circuit breaker policy to perform a programmatic rollback when the API gateway recognizes conditions that diverge from normal behavior.

Abstract: Disclosed herein are system, method, and computer program product embodiments for automatically cataloging updated Application Programming Interface (API) specifications with updated version numbers. The API specifications may have been previously published to an application exchange platform. An automatic cataloging tool installed at an API development system may identify an updated API specification committed to an API specification repository. The automatic cataloging tool may identify a base API specification that has been previously published and confirm that a change has been made. The base API specification may correspond to a particular API development branch that has been updated. The automatic cataloging tool may also apply a versioning strategy to automatically determine an updated version number for the updated API specification. The application exchange platform may then replace the previous API specification with the updated API specification and the updated version number.

Abstract: Disclosed herein are system, method, and computer program product embodiments for automatic non-code test suite generation of an application programming language (API) specification. An embodiment operates by receiving a specification of an API, wherein the API comprises a plurality of endpoints. The embodiment generates, using a parser, an abstraction model corresponding to the specification of the API, wherein the abstraction model comprises a plurality of entities corresponding to the plurality of endpoints. The embodiment identifies, based on the abstraction model, an operation that is applicable to an entity of the plurality of entities. The embodiment then generates a functional test based on a use case corresponding to the entity and the operation.

Abstract: A mobile application development environment may be maintained in association with a computing platform. A request to produce a first mobile application with a first security policy may be processed. The first mobile application may be automatically produced. The first security policy may be integrated with the first mobile application during creation of the first mobile application. The first mobile application may be provided to a mobile application provider. The first security policy may be included in the first mobile application when the first mobile application is downloaded from the mobile application provider.