File analytics systems and methods
US-12248435-B2 · Mar 11, 2025 · US
US12591542B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12591542-B2 |
| Application number | US-202418989051-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 20, 2024 |
| Priority date | Dec 20, 2023 |
| Publication date | Mar 31, 2026 |
| Grant date | Mar 31, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A directory metadata operation method, including: in response to receiving a directory query request, obtaining a query path carried therein; obtaining a prebuilt prefix directory data table and a prebuilt full load directory data table, where a key of the prefix directory data table is a prefix path of the directory metadata, which is a subpath corresponding to a hierarchy other than a default hierarchy counting from end in a path corresponding to the directory metadata, a value of the prefix directory data table is the directory metadata, a key of the full load directory data table is identification information of the directory metadata and a value thereof is the directory metadata; determining a matching result between the query path and the key of the prefix directory data table; and determining a query result based on the matching result and the full load directory data table.
Opening claim text (preview).
What is claimed is: 1 . A directory metadata operation method, comprising: in response to receiving a directory query request, obtaining a query path carried in the directory query request; obtaining a prebuilt prefix directory data table and a prebuilt full load directory data table, wherein a key of the prefix directory data table is a prefix path of directory metadata, the prefix path is a subpath corresponding to a hierarchy other than a default hierarchy counting from end in a path corresponding to the directory metadata, a value of the prefix directory data table is the directory metadata, a key of the full load directory data table is identification information of the directory metadata, and a value of the full load directory data table is the directory metadata; determining a matching result between the query path and the key of the prefix directory data table; determining a query result based on the matching result and the full load directory data table; wherein the determining the matching result between the query path and the key of the prefix directory data table comprises: determining whether the prefix path in the key of the prefix directory data table contains a target prefix path, wherein the target prefix path is a subpath corresponding to a hierarchy other than a default hierarchy counting from end in the query path; in response to the prefix path containing the target prefix path, determining the matching result to be a successful matching; in response to the prefix path not containing the target prefix path, determining the matching result to be an unsuccessful matching, wherein in response to the matching result being the successful matching, the determining the query result based on the matching result and the full load directory data table comprises: determining prefix directory metadata corresponding to the target prefix path; successively querying each hierarchy of the directory metadata below the prefix directory metadata in the query path from the full load directory data table, and determining the query result. 2 . The method according to claim 1 , wherein in response to the matching result being the unsuccessful matching, the determining the query result based on the matching result and the full load directory data table comprises: querying the full load directory data table based on the query path, and determining the query result. 3 . The method according to claim 1 , after determining the query result, the method further comprising: in response to the matching result being the unsuccessful matching and the query result being that the directory metadata corresponding to the query path is queried, creating a corresponding entry in the prefix directory data table based on the query result. 4 . The method according to claim 3 , further comprising: updating a prebuilt prefix tree based on the query result, wherein the prefix tree is a subtree of a directory tree corresponding to the directory metadata in the prefix directory data table. 5 . The method according to claim 4 , wherein the determining the matching result between the query path and the key of the prefix directory data table comprises: obtaining a prebuilt directory metadata change record table; determining whether a directory change record corresponding to the query path exists in the directory metadata change record table; in response to the directory change record corresponding to the query path existing in the directory metadata change record table, determining the matching result between the query path and the key of the prefix directory data table to be the unsuccessful matching. 6 . The method according to claim 5 , wherein the directory change record in the directory metadata change record table comprises a directory renaming record and a directory deletion record. 7 . The method according to claim 5 , further comprising: in response to receiving an invalid entry deletion command of the prefix directory data table, acquiring the directory change record from the directory metadata change record table; determining a change directory metadata that has occurred a change operation based on the directory change record; determining an association path corresponding to the change directory metadata; deleting a change entry in the prefix directory data table, wherein a prefix path corresponding to the change entry is the same as a prefix path of the association path. 8 . The method according to claim 7 , wherein the determining the association path corresponding to the change directory metadata comprises: searching for the association path corresponding to the change directory metadata from the prefix tree. 9 . The method according to claim 5 , wherein the prefix directory data table, the directory metadata change record table, and the prefix tree are all stored in a cache. 10 . A directory metadata operation apparatus, comprising: at least one processor; and a memory connected to the at least one processor in a communication way; wherein the memory stores instructions executable by the at least one processor, to: in response to receiving a directory query request, obtain a query path carried in the directory query request; obtain a prebuilt prefix directory data table and a prebuilt full load directory data table, wherein a key of the prefix directory data table is a prefix path of directory metadata, the prefix path is a subpath corresponding to a hierarchy other than a default hierarchy counting from end in a path corresponding to the directory metadata, a value of the prefix directory data table is the directory metadata, a key of the full load directory data table is identification information of the directory metadata, and a value of the full load directory data table is the directory metadata; determine a matching result between the query path and the key of the prefix directory data table; determine a query result based on the matching result and the full load directory data table; wherein to determine the matching result between the query path and the key of the prefix directory data table, the at least one processor is further caused to: determine whether the prefix path in the key of the prefix directory data table contains a target prefix path, wherein the target prefix path is a subpath corresponding to a hierarchy other than a default hierarchy counting from end in the query path; in response to the prefix path containing the target prefix path, determine the matching result to be a successful matching; in response to the prefix path not containing the target prefix path, determine the matching result to be an unsuccessful matching; wherein in response to the matching result being the successful matching, the at least one processor is further caused to determine prefix directory metadata corresponding to the target prefix path; and successively query each hierarchy of the directory metadata below the prefix directory metadata in the query path from the full load directory data table, and determine the query result. 11 . The apparatus according to claim 10 , wherein the at least one processor is further caused to: in response to the matching result being the unsuccessful matching, query the full load directory data table based on the query path, and determine the query result. 12 . The apparatus according to claim 10 , wherein the at least one processor is further caused to: after determining the query result, in response to the matching result being the unsuccessful matching and the query result being that the directory metadata corresponding to the query path is queried, create a corresponding entry in t
File search processing · CPC title
File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06) · CPC title
Presentation of query results · CPC title
using directory or table look-up (use of a directory or look-up table in file systems G06F16/13) · CPC title
Distributed file systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.