9 results about "NoSQL" patented technology

Systems and methods for a serverless tiebreaker for a shared-nothing architecture are provided. In some examples, a cloud-native service that supports serialization of writes (or write fencing), for example, via atomic operations with persistent locking and / or reservations, is used to support HA mediation instead of a separate server operating as a tiebreaker, thereby reducing costs and complexity as well as increasing availability and durability of the HA mediation functionality. For example, a fast, fully managed, serverless, key-value noSQL database service (e.g., the Amazon DynamoDB) may be used to perform one or more of maintaining the authoritative source of information regarding which node of an HA pair currently represents the primary node for serving data from a particular dataset, persisting HA metadata, and / or assisting in the failover and failback processes.

The invention discloses a method and system for executing SQL query in a NoSQL database, and the method comprises the steps: extracting the specific semantics of NoSQL into standardized rule slot plug-ins, registering the standardized rule slot plug-ins in a central warehouse, carrying out the triggering binding of all rule slot plug-ins and an SQL parser, and enabling the SQL parser to carry out the query according to the current SQL query and the triggering binding result. According to the method, the corresponding rule slot plug-in is automatically queried in the central warehouse for semantic compensation, the rule slot plug-in can be automatically instantiated during analysis, seamless writing of standard SQL and NoSQL extension in the same statement is ensured, seamless completion from a common SQL to a complete SQL with NoSQL specific semantics is realized, any NoSQL specific semantics can be expressed in a zero-loss manner, and the method is suitable for large-scale popularization and application. The migration cost and the maintenance cost from the NoSQL to the SQL are remarkably reduced, and analysts can directly use the standard SQL to query the NoSQL data in the NoSQL database.

The invention discloses a corrosion environment bridge cable life prediction method and system based on data analysis, and relates to the technical field of bridge engineering, the system collects environmental data and cable corrosion data in real time through an integrated sensor group, and the environmental data and the cable corrosion data are transmitted and preprocessed through a wireless network LoRa and then stored in a non-relational database NoSQL. The method comprises the following steps: extracting health feature data, calculating a cable health index Lfs, and carrying out preliminary evaluation on the cable health index Lfs and a preset cable safety threshold A; and if the inhaul cable is in a healthy state, triggering secondary evaluation, deeply analyzing surface characteristics and environmental characteristics of the inhaul cable, and calculating a surface corrosion influence index Bmy and an environmental influence index Hjx of the inhaul cable. And calculating a comprehensive corrosion rate prediction index FYC according to the indexes, and comparing the comprehensive corrosion rate prediction index FYC with a preset corrosion rate threshold B to generate corresponding early warning information. The system aims at monitoring and evaluating the corrosion state of the bridge inhaul cable in real time, improving the safety and reliability of a bridge and taking maintenance measures in time.

The present embodiments relate to implementing change data on no-master NoSQL data stores. An optimized node can be identified from a plurality of NoSQL data storage nodes and a specialized node can be connected (e.g., collocated) to the optimized node. The specialized node can maintain change data capture (CDC) data provided by client nodes in a hash map that can be used as a point of truth for coordinating CDC data across the plurality of NoSQL data storage nodes. The plurality of NoSQL data storage nodes can identify and coordinate all read / write data obtained from multiple client devices in a geographically separated large-scale (e.g., planet scale) system to identify change data in a distributed data store. The specialized data can provide read data to devices in the large-scale system to reconcile inconsistencies in change data across nodes in the large-scale system.

Generating queries in a heterogeneous cloud computing environment is provided. The method comprises transforming disparate statistical formats into a unified representation to standardize statistical metadata between relational databases and NoSQL databases. SQL-derived NoSQL statistics are integrated into a unified repository according to the unified representation. Mapped NoSQL statistics are integrated into relational database query optimizers. An optimal predicate pushdown strategy and an execution plan for a query across heterogeneous databases are determined according to the standardized statistical metadata. The query to the heterogeneous databases is then executed according to the relational database query optimizers and the optimal pushdown strategy and execution plan.

The application discloses a method and system for executing SQL query in NoSQL database, the method extracts the unique semantics of NoSQL into standardized rule slot plug-ins and registers the rule slot plug-ins into a central repository, and binds all the rule slot plug-ins with a SQL parser, the SQL parser can automatically query the corresponding rule slot plug-in for semantic compensation in the central repository according to the current SQL query and the binding result, and the rule slot plug-in can be automatically instantiated during parsing, so that the standard SQL and NoSQL extension can be seamlessly written in the same statement, the seamless completion from the normal SQL to the complete SQL with the unique semantics of NoSQL is realized, any unique semantics of NoSQL can be expressed with zero loss, the migration cost and maintenance cost from NoSQL to SQL are significantly reduced, and analysts can directly use the standard SQL to query NoSQL data in the NoSQL database.

Database management techniques can gauge real-time caching states of no-schema-based (noSQL) databases (DBs) during runtime operation by maintaining a log table to reflect modifications to the noSQL DB. The log table is maintained by adding row entries to reflect modifications to the noSQL DB and therefore does not requiring querying the noSQL DB. The log table may then be deduplicated to remove stale entries and queried to generate a cost table reflecting a real-time caching state of the noSQL DB.

A procedure (400) involves accessing a distributed database (140) containing a plurality of clusters (210), each cluster containing a plurality of partitions (212), and each cluster being configured to receive read and write operations (20, 21). The procedure involves receiving, on a second cluster (210B), a plurality of changes (350) for a second table (250B) and storing the plurality of changes in a replication log (351). The procedure also involves asynchronously replicating the plurality of changes from the second table to a first table (250A) and maintaining a respective change stream position (214A) that tracks a respective position in the replication log indicating one or more changes that have been replicated.The procedure involves receiving a read request at the first cluster (210A) requesting one or more rows of the first table, and returning the respective change stream position.

A method for change data capture state tracking includes accessing a distributed database including a plurality of clusters, each cluster of the plurality of clusters including a respective plurality of partitions, each cluster of the plurality of clusters configured to receive read and write operation. The method includes receiving, at a second cluster, a plurality of changes for a second table and storing the plurality of changes at a replication log. The method also includes asynchronously replicating the plurality of changes from the second table to a first table and maintaining a respective change stream position tracking a respective position in the replication log indicating one or more changes of the plurality of changes that have been replicated. The method includes receiving a read request at the first cluster requesting one or more rows of the first table and returning the respective change stream position.