Content Classes for Object Storage Indexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face difficulties in searching for specific content across large object storage systems due to varying metadata formats and storage locations, leading to inefficient indexing and resource-intensive solutions.
Innovation Solution
The implementation of content classes with user-defined properties, such as XML, JSON, and regular expression patterns, enables automated metadata enhancement and uniform indexing across different data sources, allowing for structured querying and efficient storage resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a general indexing mechanism is implemented to enable searching across diverse object data sources with varying metadata formats, then search capability and adaptability are improved, but storage resources consumed by the index increase significantly
Solution Approach 1:
The patent extracts and indexes only specific selected metadata fields rather than all metadata. The system allows users to define which metadata fields to index, extracting only the relevant portions needed for search while leaving other metadata unindexed, thus reducing index storage requirements while maintaining search functionality.
Solution Approach 2:
The system implements partial indexing by allowing selective indexing of metadata fields. Instead of indexing all metadata comprehensively, the system indexes only the necessary subset of fields that users specify, achieving adequate search coverage with reduced storage overhead.
2Reliability
If comprehensive metadata indexing is performed across all object data sources, then search completeness is improved, but indexing complexity and processing time increase
Solution Approach 1:
The patent segments the indexing process into manageable components. It divides metadata into different fields and allows selective indexing of individual fields. The system also segments the indexing operation into extraction, transformation, and loading phases, making the overall process less complex and more controllable.
Solution Approach 2:
The system implements dynamic indexing where users can flexibly define and modify which metadata fields to index based on their specific needs. The indexing configuration is not fixed but can be adapted dynamically, allowing the system to balance between search completeness and indexing complexity based on user requirements.
3Quantity of substance
If selective indexing of specific metadata fields is implemented, then storage efficiency is improved, but search flexibility deteriorates
Solution Approach 1:
The patent creates a universal indexing framework that can handle multiple metadata formats and fields through a unified interface. The system uses a standardized schema that can accommodate various metadata types (XML, JSON, key-value pairs) while maintaining consistent indexing operations, thus preserving search flexibility across diverse data sources.
Solution Approach 2:
The system changes the parameter of indexability by allowing dynamic selection of which metadata fields to index. Users can modify the set of indexed fields based on their search requirements, enabling the system to adapt between storage efficiency and search flexibility by adjusting the indexing parameters rather than being fixed in one approach.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In some examples, a system may use content classes to manage indexing of object data. A content class may include a set of one or more content properties. Each content property may include a name, an expression for extracting data, and an expression type. When object data is received, such as for indexing, the expression type of each content property may be compared with the data type of the received data. Based at least in part on determining that the expression type matches the data type, the system may extract a data value from the received data in accordance with the expression. The system may save the extracted data value to a data structure in association with the name of the content property, and may subsequently use the data value and the name of the content property when creating an index for the object data.