Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A computer-implemented method for generating a platform-independent metadata catalog framework of a first database system, the method comprising: receiving, at the first database system, a metadata object; determining a version of the received metadata object; responsive to determining that a metadata catalog, having catalog entries associated with unique versions of metadata objects, does not include a catalog entry associated with the version of the received metadata object: creating a catalog entry in the metadata catalog, the created catalog entry being associated with the version of the received metadata object, and generating a version number based on the version of the received metadata, the generated version number being associated with the created catalog entry; determining a change to the metadata object based on the created catalog entry; generating, based on the change, a data exchange element that includes a JavaScript Object Notation (JSON) string; updating a metadata log to include the data exchange element and a command associated with the data exchange element, wherein the command corresponds to the change to the metadata object; and transmitting the metadata log to a second database system for replaying the metadata log at the second database system such that the command is executed when the second database system enters a recovery mode, the second database system having a different database version from that of the first database system.
This invention relates to a computer-implemented method for generating a platform-independent metadata catalog framework that enables seamless metadata synchronization between database systems with different versions. The method addresses the challenge of maintaining consistency and compatibility when transferring metadata between heterogeneous database environments, ensuring that changes are accurately replicated without version conflicts. The process begins by receiving a metadata object at a first database system and determining its version. If the metadata catalog—which stores entries linked to unique metadata object versions—does not contain an entry for the received object’s version, a new catalog entry is created, and a version number is generated and associated with it. The system then identifies changes to the metadata object based on the catalog entry and generates a data exchange element containing a JSON string representing those changes. This element, along with a corresponding command, is logged in a metadata log. The log is transmitted to a second database system, which replays it during recovery mode, executing the commands to replicate the metadata changes despite differences in database versions. This approach ensures version-agnostic metadata synchronization, preserving integrity across diverse database systems.
2. The method of claim 1 , further comprising outputting the version number associated with the created catalog entry.
Technical Summary: This invention relates to catalog management systems, specifically methods for tracking and outputting version information for catalog entries. The core problem addressed is the need to maintain accurate version control in catalog systems to ensure traceability and consistency of data entries. The method involves creating a catalog entry in a catalog system, where the catalog entry includes a version number. The version number is associated with the catalog entry to track changes and updates. Additionally, the method includes outputting the version number associated with the created catalog entry, allowing users or systems to identify the specific version of the catalog entry being referenced or modified. This output can be used for auditing, synchronization, or version comparison purposes. The method ensures that each catalog entry is uniquely identifiable by its version number, enabling better version control and reducing errors in catalog management. The output of the version number provides transparency and traceability, which is critical in systems where multiple users or processes may interact with the catalog. This approach is particularly useful in environments where catalog data is frequently updated or shared across different systems or applications.
3. The method of claim 1 , further comprising responsive to determining that the metadata catalog includes a catalog entry associated with the version of the received metadata object, outputting the catalog entry associated with the version of the received metadata object.
This invention relates to metadata management systems, specifically improving the retrieval and version tracking of metadata objects in a catalog. The problem addressed is the difficulty in efficiently locating and accessing specific versions of metadata objects within a large, dynamic metadata catalog. The solution involves a method for managing metadata objects that includes receiving a metadata object, determining whether the metadata catalog contains an entry associated with the version of the received metadata object, and if such an entry exists, outputting that catalog entry. The method ensures that users can quickly retrieve the correct version of a metadata object without manual searching or version conflicts. The system may also include steps for generating or updating catalog entries when a new version of a metadata object is received, ensuring the catalog remains current. This approach enhances metadata version control, reduces retrieval time, and improves system reliability by maintaining accurate version records. The invention is particularly useful in environments where metadata objects are frequently updated, such as data governance, enterprise information management, or software development systems.
4. The method of claim 1 , further comprising responsive to determining that the metadata catalog includes one or more catalog entries associated with previous versions of the received metadata object, changing the version number associated with the created catalog entry to a value that is indicative of a version that is later than the one or more catalog entries associated with the previous version of the received metadata object.
This invention relates to metadata management systems, specifically handling versioning of metadata objects in a catalog. The problem addressed is ensuring proper version tracking when new metadata objects are added to a catalog, particularly when previous versions of the same object already exist. The system receives a metadata object and creates a catalog entry for it. If the catalog already contains entries for earlier versions of the same metadata object, the system updates the version number of the new entry to reflect that it is a later version than any existing entries. This ensures version consistency and prevents conflicts in the catalog. The method involves comparing the received metadata object with existing catalog entries to identify prior versions, then adjusting the version number of the new entry accordingly. This approach helps maintain an organized and accurate historical record of metadata changes, which is critical for data governance, compliance, and traceability in large-scale data systems. The solution is particularly useful in environments where metadata evolves over time, such as in data lakes, enterprise data warehouses, or metadata-driven applications.
5. The method of claim 1 , further comprising identifying a set of fields included in the received metadata object, each field comprising a definition of data included in the first database system, wherein the creating a catalog entry in the metadata catalog is based on the identified set of fields included in received metadata object.
This invention relates to metadata management in database systems, specifically improving the organization and accessibility of metadata objects. The problem addressed is the difficulty in efficiently cataloging and retrieving metadata from different database systems, particularly when metadata objects contain complex or varied field structures. The method involves receiving a metadata object from a first database system, where this object contains information about the structure and data definitions within that system. The method then identifies a set of fields within the received metadata object, with each field representing a specific data definition in the first database system. Based on these identified fields, a catalog entry is created in a centralized metadata catalog. This catalog entry is structured according to the fields detected in the metadata object, ensuring that the catalog accurately reflects the data definitions of the original database system. The process ensures that metadata from diverse database systems can be systematically organized in a unified catalog, facilitating easier search, retrieval, and integration of metadata across different systems. This approach enhances interoperability and simplifies metadata management in environments with multiple database systems.
6. The method of claim 5 , wherein the determining that the metadata catalog includes one or more catalog entries associated with previous versions of the received metadata object comprises comparing the definition of data of each field of the received metadata object with the definition of data of each field of the unique metadata object associated with each catalog entry included in the metadata catalog.
This invention relates to metadata management systems, specifically for tracking and comparing versions of metadata objects in a catalog. The problem addressed is the difficulty in efficiently identifying and managing previous versions of metadata objects within a metadata catalog, which is critical for maintaining data integrity, compliance, and historical tracking in large-scale data environments. The method involves determining whether a metadata catalog contains entries associated with previous versions of a received metadata object. This is done by comparing the data definitions of each field in the received metadata object with the data definitions of each field in the unique metadata objects linked to the catalog entries. The comparison process ensures that even minor differences in field definitions are detected, allowing the system to accurately identify whether the received metadata object is a new version of an existing entry or a completely new object. This enables version tracking, conflict resolution, and historical analysis of metadata changes over time. The method supports data governance by ensuring that all versions of metadata objects are properly cataloged and retrievable, which is essential for auditing, compliance, and data lineage purposes. The solution is particularly useful in environments where metadata evolves frequently, such as in enterprise data lakes, data warehouses, or cloud-based data platforms.
7. The method of claim 5 , wherein each catalog entry comprises a version number that is indicative of the unique version of the metadata object.
Technical Summary: This invention relates to a system for managing metadata objects in a catalog, addressing the challenge of tracking and identifying different versions of metadata objects to ensure data integrity and consistency. The system includes a catalog that stores entries, each representing a metadata object. Each catalog entry contains a version number that uniquely identifies the specific version of the associated metadata object. This version number allows users and systems to distinguish between different iterations of the same metadata object, ensuring that the correct version is accessed and used. The version number may be incremented or updated whenever the metadata object is modified, providing a clear and traceable history of changes. This approach helps prevent conflicts, errors, and inconsistencies that can arise when multiple versions of metadata objects are in use. The system may also include mechanisms for querying, retrieving, and comparing different versions of metadata objects based on their version numbers, enhancing version control and management capabilities. The invention is particularly useful in environments where metadata objects are frequently updated or shared across multiple systems, ensuring that all users and applications work with the correct and most up-to-date versions.
8. The method of claim 7 , wherein the assigned value to the version number of the created catalog entry is larger than the version numbers of the one or more catalog entries associated with the previous version of the received metadata object.
This invention relates to version management in catalog systems, specifically ensuring proper version numbering when creating new catalog entries from metadata objects. The problem addressed is maintaining version consistency when updating catalog entries derived from metadata objects, preventing version number conflicts or regressions. The method involves creating a new catalog entry from a received metadata object, where the metadata object represents an updated version of an existing catalog entry. The key innovation is assigning a version number to the new catalog entry that is larger than all version numbers of catalog entries associated with the previous version of the metadata object. This ensures the new entry has a higher version number than any prior versions, maintaining chronological order and preventing version number conflicts. The process includes receiving a metadata object, identifying one or more existing catalog entries associated with a previous version of that metadata object, and then creating a new catalog entry from the received metadata object. The version number assignment rule guarantees that the new entry's version number is strictly greater than any existing versions of the same metadata object, which is critical for systems where version numbers must reflect true chronological updates. This approach is particularly useful in distributed systems or environments where multiple versions of metadata objects may exist simultaneously.
9. The method of claim 5 , wherein a field in the received metadata object comprises a type and size.
A system and method for processing metadata objects in a data management environment addresses the challenge of efficiently handling and interpreting metadata to improve data organization and retrieval. The invention involves receiving a metadata object containing structured information about data, where the metadata object includes fields that define attributes of the data. A key aspect is that at least one field within the metadata object specifies both a type and a size, allowing for precise classification and storage of the associated data. The type field indicates the data category (e.g., text, numeric, binary), while the size field specifies the storage requirements or dimensions of the data. This structured approach ensures compatibility with various data processing systems and enables accurate data validation, indexing, and retrieval. The method may also involve parsing the metadata object to extract the type and size information, which can then be used to optimize storage allocation, data compression, or query performance. By standardizing metadata representation, the invention enhances interoperability between different data systems and reduces errors in data interpretation. The solution is particularly useful in large-scale data environments where metadata accuracy and efficiency are critical for maintaining data integrity and accessibility.
10. The method of claim 9 , wherein the size of the received metadata object is based on the sizes of each field in the identified set.
This invention relates to data processing systems that handle metadata objects, particularly focusing on optimizing the size of metadata objects based on the sizes of their constituent fields. The problem addressed is the inefficient use of storage and bandwidth when metadata objects are transmitted or stored without considering the actual size requirements of their fields, leading to wasted resources. The method involves receiving a metadata object that contains multiple fields, each with a defined size. The system identifies a set of fields within the metadata object and determines the size of each field in this set. The size of the received metadata object is then adjusted based on the sizes of these fields, ensuring that the metadata object only occupies the necessary storage or bandwidth. This approach optimizes resource usage by dynamically sizing the metadata object according to the actual data it contains, rather than using a fixed or overly large size. The method may also include additional steps such as validating the metadata object to ensure it meets certain criteria before processing, and dynamically adjusting the metadata object's size in response to changes in the field sizes. This ensures that the metadata object remains efficient and adaptable to varying data requirements. The invention is particularly useful in systems where metadata objects are frequently transmitted or stored, such as in distributed computing environments or databases, where minimizing resource consumption is critical.
11. The method of claim 9 , wherein the position of a field in the received metadata object is based on the sizes of each prior field in the identified set.
This invention relates to data processing systems that handle metadata objects, specifically addressing the challenge of efficiently organizing and accessing metadata fields within a structured object. The method involves dynamically determining the position of a field within a metadata object based on the cumulative sizes of all preceding fields in a predefined set. This approach ensures that fields are placed in a way that optimizes storage efficiency and retrieval speed, particularly in systems where metadata objects must be parsed or processed sequentially. The method first identifies a set of fields from the metadata object that are relevant for positioning. For each subsequent field, its position is calculated by summing the sizes of all prior fields in the set, ensuring that each field is placed at an offset that accounts for the combined storage requirements of the preceding fields. This technique is particularly useful in systems where metadata objects are transmitted or stored in a compact format, such as binary or serialized data structures, where field positioning directly impacts performance. The method may be applied in various applications, including database management, file systems, or network protocols, where metadata must be efficiently encoded, decoded, or traversed. By dynamically adjusting field positions based on their sizes, the invention improves data handling efficiency and reduces processing overhead.
12. The method of claim 1 , further comprising outputting one of the catalog entries in the metadata catalog in a platform-independent format, and outputting the version number of the outputted catalog entry.
This invention relates to data cataloging systems, specifically methods for managing and retrieving metadata entries in a structured catalog. The problem addressed is the need for efficient, version-controlled access to metadata entries across different platforms, ensuring consistency and traceability in data management. The method involves maintaining a metadata catalog containing multiple catalog entries, each associated with a version number. When a catalog entry is requested, the system outputs the entry in a platform-independent format, ensuring compatibility across different systems. Additionally, the version number of the outputted catalog entry is provided, allowing users to track changes and maintain consistency. This versioning mechanism helps in auditing and ensuring data integrity, particularly in environments where metadata is frequently updated or accessed by multiple systems. The system may also include mechanisms for updating catalog entries, where new versions are generated and stored while maintaining references to previous versions. This ensures that historical data remains accessible, supporting compliance and traceability requirements. The platform-independent format allows seamless integration with various applications, reducing the need for format conversions and minimizing errors. By combining version tracking with platform-independent output, this method enhances metadata management, making it more reliable and adaptable in diverse computing environments. The solution is particularly useful in large-scale data systems where metadata must be shared across heterogeneous platforms while maintaining accuracy and version control.
13. The method of claim 12 , wherein the platform-independent format includes JSON, XML, YAML, REBOL, Gellish, Atom, HOCON, CVS, or any combination thereof.
The invention relates to data processing systems that handle platform-independent data formats for interoperability between different computing environments. The core problem addressed is the difficulty of exchanging data between systems that use different data representation formats, leading to compatibility issues and inefficiencies in data integration. The method involves converting data between a source format and a target format, where the target format is platform-independent and selected from a predefined set of standardized formats. These formats include JSON, XML, YAML, REBOL, Gellish, Atom, HOCON, and CSV, or any combination thereof. The conversion process ensures that the data remains intact and interpretable across different systems, regardless of their native data representation methods. The method may also involve validating the converted data to confirm its structural and semantic integrity before transmission or storage. By using widely adopted, platform-independent formats, the invention enables seamless data exchange between heterogeneous systems, reducing the need for custom data translation solutions. This approach improves interoperability, simplifies system integration, and enhances data portability across diverse computing environments. The method is particularly useful in scenarios where data must be shared between applications, services, or devices that do not share a common data representation standard.
14. A non-transitory computer-readable storage medium including instructions to perform operations comprising: receiving, at a first database system, a metadata object; determining a version of the received metadata object; responsive to determining that a metadata catalog, having catalog entries associated with unique versions of metadata objects, does not include a catalog entry associated with the version of the received metadata object: creating a catalog entry in the metadata catalog, the created catalog entry being associated with the version of the received metadata object, and generating a version number based on the version of the received metadata, the generated version number being associated with the created catalog entry; determining a change to the metadata object based on the created catalog entry; generating, based on the change, a data exchange element that includes a JavaScript Object Notation (JSON) string; updating a metadata log to include the data exchange element and a command associated with the data exchange element, wherein the command corresponds to the change to the metadata object; and transmitting the metadata log to a second database system for replaying the metadata log at the second database system such that the command is executed when the second database system enters a recovery mode, the second database system having a different database version from that of the first database system.
This invention relates to a system for managing metadata objects across different database versions, addressing the challenge of maintaining consistency and enabling recovery when metadata changes occur. The system involves a first database system that receives a metadata object and determines its version. If the metadata catalog, which tracks unique versions of metadata objects, lacks an entry for the received version, a new catalog entry is created, and a version number is generated and associated with it. The system then identifies changes to the metadata object based on the catalog entry and generates a data exchange element containing a JSON string representing those changes. This element, along with a corresponding command, is logged in a metadata log. The log is transmitted to a second database system, which may operate on a different database version. When the second system enters recovery mode, it replays the log, executing the commands to apply the metadata changes. This ensures synchronization and recovery across disparate database versions, mitigating inconsistencies during updates or failures. The approach leverages structured data (JSON) and version tracking to facilitate seamless metadata propagation and recovery.
15. A computer-implemented database recovery system, the system comprising: one or more data processors; and a computer-readable storage medium encoded with instructions for commanding the one or more data processors to perform operations comprising: receiving, at a first database system, a metadata object; determining a version of the received metadata object; responsive to determining that a metadata catalog, having catalog entries associated with unique versions of metadata objects, does not include a catalog entry associated with the version of the received metadata object: creating a catalog entry in the metadata catalog, the created catalog entry being associated with the version of the received metadata object, and generating a version number based on the version of the received metadata, the generated version number being associated with the created catalog entry; determining a change to the metadata object based on the created catalog entry; generating, based on the change, a data exchange element that includes a JavaScript Object Notation (JSON) string; updating a metadata log to include the data exchange element and a command associated with the data exchange element, wherein the command corresponds to the change to the metadata object; and transmitting the metadata log to a second database system for replaying the metadata log at the second database system such that the command is executed when the second database system enters a recovery mode, the second database system having a different database version from that of the first database system.
This invention relates to a computer-implemented database recovery system designed to facilitate metadata synchronization and recovery between database systems of different versions. The system addresses the challenge of maintaining consistency and enabling recovery in distributed database environments where systems may operate on different software versions. The system includes one or more data processors and a computer-readable storage medium with instructions for managing metadata objects across databases. The system receives a metadata object at a first database system and determines its version. If the metadata catalog—a repository of unique metadata object versions—does not contain an entry for the received version, the system creates a new catalog entry and generates a version number for it. The system then identifies changes to the metadata object based on the catalog entry and generates a data exchange element containing a JSON string representing those changes. This element, along with an associated command, is logged in a metadata log. The log is transmitted to a second database system, which replays it during recovery mode, executing the commands to synchronize metadata even if the second system operates on a different database version. This ensures seamless recovery and consistency across heterogeneous database environments.
16. The system of claim 15 , the operations further comprising identifying a set of fields included in the received metadata object, each field comprising a definition of data included in the first database system, wherein the creating a catalog entry in the metadata catalog is based on the identified set of fields included in received metadata object.
A system for managing metadata in database environments addresses the challenge of efficiently organizing and retrieving metadata from multiple database systems. The system receives a metadata object from a first database system, where the metadata object contains information about the structure and data within that system. The system processes this metadata object by identifying a set of fields included in the metadata, where each field defines a specific type of data stored in the first database system. Based on these identified fields, the system creates a catalog entry in a centralized metadata catalog, ensuring that the metadata is structured and accessible for further use. This catalog entry serves as a reference point for the metadata, allowing users or other systems to query and retrieve information about the database structure without directly accessing the original database. The system may also include additional operations such as validating the metadata object against predefined rules or standards before cataloging it, ensuring data integrity and consistency. By automating the extraction and cataloging of metadata, the system simplifies metadata management across heterogeneous database environments, improving efficiency and reducing errors in data governance.
17. The system of claim 16 , wherein each catalog entry comprises a version number that is indicative of the unique version of the metadata object.
Technical Summary: This invention relates to a system for managing metadata objects in a catalog, addressing the challenge of tracking and identifying different versions of metadata objects to ensure data integrity and consistency. The system includes a catalog that stores entries, each representing a metadata object. Each catalog entry contains a version number that uniquely identifies the specific version of the associated metadata object. This version number allows the system to distinguish between different iterations of the same metadata object, enabling version control and ensuring that users or applications can access the correct version of the metadata. The version number may be incremented or updated whenever the metadata object is modified, ensuring traceability and preventing conflicts when multiple versions of the same metadata object exist. This feature is particularly useful in environments where metadata objects are frequently updated or shared across multiple systems, as it provides a reliable mechanism for version tracking and synchronization. The system may be part of a larger data management or metadata management framework, where accurate versioning is critical for maintaining data accuracy and consistency.
18. The system of claim 17 , wherein the assigned value to the version number of the created catalog entry is larger than the version numbers of the one or more catalog entries associated with the previous version of the received metadata object.
This invention relates to version management in catalog systems, specifically addressing the challenge of tracking and organizing different versions of metadata objects within a catalog. The system ensures that when a new version of a metadata object is received, a corresponding catalog entry is created with an updated version number that is higher than the version numbers of all existing catalog entries associated with the previous version of that metadata object. This prevents version conflicts and maintains a clear, sequential version history. The system includes a catalog manager that processes metadata objects, generates catalog entries, and assigns version numbers to ensure proper versioning. The version number assignment logic guarantees that each new catalog entry for a metadata object has a version number greater than any prior versions, enabling accurate version tracking and retrieval. The system may also include a storage component to store catalog entries and a retrieval mechanism to access specific versions of metadata objects based on their version numbers. This approach ensures that users can reliably access the most recent version of a metadata object while maintaining a complete history of all previous versions.
19. The system of claim 16 , wherein a field in the received metadata object comprises a type and size.
**Technical Summary for Prior Art Search** This invention relates to data processing systems that handle metadata objects, particularly focusing on the structure and management of metadata fields. The system is designed to improve data organization and retrieval by standardizing the way metadata is stored and accessed. The core system includes a metadata processing module that receives metadata objects from various sources. These metadata objects contain structured data fields, each of which includes a defined type (e.g., string, integer, date) and a specified size (e.g., maximum length, bit width). The type and size attributes ensure consistency in data representation, preventing errors caused by mismatched data formats. The system further includes a validation mechanism that checks incoming metadata objects against predefined rules, ensuring that each field adheres to its specified type and size. This validation step helps maintain data integrity and compatibility across different applications or databases. Additionally, the system may include a transformation module that converts metadata objects into a standardized format, allowing seamless integration with other systems. This is particularly useful in environments where metadata must be shared or processed by multiple applications with varying requirements. The invention addresses the problem of inconsistent metadata handling in data systems, where mismatched field types or sizes can lead to errors, inefficiencies, or data loss. By enforcing strict type and size definitions, the system ensures reliable data processing and interoperability.
20. The system of claim 19 , wherein the size of the received metadata object is based on the sizes of each field in the identified set.
The system relates to data processing and metadata management, specifically addressing the challenge of efficiently handling metadata objects in a computing environment. The system dynamically determines the size of a metadata object based on the sizes of individual fields within a predefined set of fields. This approach ensures that the metadata object is optimized for storage and transmission, reducing overhead and improving performance. The system identifies a set of fields relevant to the metadata object, analyzes the size of each field, and calculates the overall size of the metadata object accordingly. This dynamic sizing mechanism allows the system to adapt to varying data requirements, ensuring efficient resource utilization. The system may also include mechanisms for validating the metadata object, ensuring data integrity and consistency. Additionally, the system can process the metadata object to extract or modify field values, enabling flexible data manipulation. The dynamic sizing feature is particularly useful in environments where metadata objects must be transmitted or stored with minimal overhead, such as distributed systems or cloud-based applications. By adjusting the metadata object size based on field sizes, the system enhances efficiency and scalability.
Unknown
January 7, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.