Method and apparatus for searching metadata

• US 9,130,952 B2
• Filed: 02/06/2014
• Issued: 09/08/2015
• Est. Priority Date: 08/04/2006
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Colclasure, Kaelin Lee, Tucker, Ruxton J., Suinn, Bradley R M, Hornkvist, John Martin, Arrouye, Yan, Callaghan, Brent
• Primary Examiner(s): LU, KUEN S
• Application Number:
  US14/174,726
• Publication Number:
  US 20140189844A1
• Time in Patent Office: 579 Days
• Field of Search: 707/802, 707/765, 707/769
• US Class Current: 1/1
• CPC Class Codes: G06F 16/14 Details of searching files based on file metadata
• CPC Class Codes: G06F 16/2453 Query optimisation
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

Methods and apparatuses for searching metadata are described herein. In one embodiment, an example of a process for search metadata includes, hut is not limited to, in response to a search query for metadata stored in one or more of metadata stores, the search query is partitioned into multiple search query segments. Thereafter, searches corresponding to the search query segments are performed, where each search is performed independently within the one or more metadata stores. Other methods and apparatuses are also described.

Claims

1. A computer-implemented method for searching metadata, the method comprising:

in response to a first request received from a first remote metadata store (MDS) peer instance of a first remote peer for accessing metadata stored in a local MDS of a local peer, creating and initiating by a peer manager a first local MDS peer instance to establish a first communications channel with the first remote MDS peer instance to allow the first remote peer accessing the metadata stored in the local MDS of the local peer, wherein the first local MDS peer instance operates as a first proxy for a first peer MDS process specifically for handling the first request for accessing the metadata stored in the local MDS over the first communications channel;

in response to a second request received from a local client of the local peer for accessing metadata stored in a second remote peer, creating and initiating by the peer manager a second local MDS peer instance to establish a second communications channel with a second remote MDS peer instance of the second remote peer to allow the local client accessing the metadata stored in the second remote peer, wherein the second local MDS peer instance operates as a second proxy for a second peer MDS process specifically for handling the second request for accessing the metadata stored in the second remote peer over second communications channel; and

managing by the peer manager the first and second communications channels via the first and second MDS peer instances, respectively.

2. The method of claim 1, wherein the peer manager is configured to maintain a plurality of communications channels via a corresponding one of local MDS peer instances for exchanging metadata with a plurality of remote peers, respectively.

3. The method of claim 2, further comprising:

receiving a first signal from the first remote peer indicating that the first communications channel is no longer needed; and

in response to the first signal, destroying by the peer manager the first local MDS peer instance to shut down the first communications channel.

4. The method of claim 2, further comprising:

receiving a second signal from the local client indicating that the second communications channel is no longer needed; and

in response to the second signal, destroying by the peer manager the second local MDS peer instance to shut down the second communications channel.

5. The method of claim 1, wherein the first local MDS peer instance is configured to operate as an MDS server with respect to the first remote MDS peer instance.

6. The method of claim 5, wherein the second local MDS peer instance is configured to operate as an MDS client with respect to the second remote MDS peer instance.

7. The method of claim 1, wherein creating and initiating the first local MDS peer instance comprises:

authenticating a first user of the first remote peer based on a first user credential of the first user received from the first remote peer;

transmitting to the first remote peer a first MDS channel token representing an access permission to a first storage volume associated with the local peer that stores the requested metadata; and

providing the first user of the first remote peer access of the first storage volume based on the first MDS channel token.

8. The method of claim 1, wherein creating and initiating the second local MDS peer instance comprises:

transmitting a second user credential of a second user of the local client to the second remote peer to allow the second remote peer to authenticate the second user;

receiving from the second remote peer a second MDS channel token representing an access permission to a second storage volume associated with the second remote peer; and

providing the second user access of the second storage volume of the second remote peer based on the second MDS channel token.

9. A non-transitory machine-readable medium having instructions stored therein, which when executed by a machine, cause the machine to perform a method, the method comprising:

in response to a first request received from a first remote metadata store (MDS) peer instance of a first remote peer for accessing metadata stored in a local MDS of a local peer, creating and initiating by a peer manager a first local MDS peer instance to establish a first communications channel with the first remote MDS peer instance to allow the first remote peer accessing the metadata stored in the local MDS of the local peer, wherein the first local MDS peer instance operates as a first proxy for a first peer MDS process specifically for handling the first request for accessing the metadata stored in the local MDS over the first communications channel;

in response to a second request received from a local client of the local peer for accessing metadata stored in a second remote peer, creating and initiating by the peer manager a second local MDS peer instance to establish a second communications channel with a second remote MDS peer instance of the second remote peer to allow the local client accessing the metadata stored in the second remote peer, wherein the second local MDS peer instance operates as a second proxy for a second peer MDS process specifically for handling the second request for accessing the metadata stored in the second remote peer over second communications channel; and

managing by the peer manager the first and second communications channels via the first and second MDS peer instances, respectively.

10. The non-transitory machine-readable medium of claim 9, wherein the peer manager is configured to maintain a plurality of communications channels via a corresponding one of local MDS peer instances for exchanging metadata with a plurality of remote peers, respectively.

11. The non-transitory machine-readable medium of claim 10, wherein the method further comprises:

receiving a first signal from the first remote peer indicating that the first communications channel is no longer needed; and

in response to the first signal, destroying by the peer manager the first local MDS peer instance to shut down the first communications channel.

12. The non-transitory machine-readable medium of claim 10, wherein the method further comprises:

receiving a second signal from the local client indicating that the second communications channel is no longer needed; and

in response to the second signal, destroying by the peer manager the second local MDS peer instance to shut down the second communications channel.

13. The non-transitory machine-readable medium of claim 9, wherein the first local MDS peer instance is configured to operate as an MDS server with respect to the first remote MDS peer instance.

14. The non-transitory machine-readable medium of claim 13, wherein the second local MDS peer instance is configured to operate as an MDS client with respect to the second remote MDS peer instance.

15. The non-transitory machine-readable medium of claim 9, wherein creating and initiating the first local MDS peer instance comprises:

authenticating a first user of the first remote peer based on a first user credential of the first user received from the first remote peer;

transmitting to the first remote peer a first MDS channel token representing an access permission to a first storage volume associated with the local peer that stores the requested metadata; and

providing the first user of the first remote peer access of the first storage volume based on the first MDS channel token.

16. The non-transitory machine-readable medium of claim 9, wherein creating and initiating the second local MDS peer instance comprises:

transmitting a second user credential of a second user of the local client to the second remote peer to allow the second remote peer to authenticate the second user;

receiving from the second remote peer a second MDS channel token representing an access permission to a second storage volume associated with the second remote peer; and

providing the second user access of the second storage volume of the second remote peer based on the second MDS channel token.

17. A data processing system, comprising:

a processor;

a local metadata store (MDS) for storing metadata; and

a peer manager executed in by the processor, the peer manager configured to

in response to a first request received from a first remote MDS peer instance of a first remote peer for accessing metadata stored in a local MDS of the data processing system as a local peer, create and initiate a first local MDS peer instance to establish a first communications channel with the first remote MDS peer instance to allow the first remote peer accessing the metadata stored in the local MDS of the local peer, wherein the first local MDS peer instance operates as a first proxy for a first peer MDS process specifically for handling the first request for accessing the metadata stored in the local MDS over the first communications channel,

in response to a second request received from a local client of the local peer for accessing metadata stored in a second remote peer, create and initiate a second local MDS peer instance to establish a second communications channel with a second remote MDS peer instance of the second remote peer to allow the local client accessing the metadata stored in the second remote peer, wherein the second local MDS peer instance operates as a second proxy for a second peer MDS process specifically for handling the second request for accessing the metadata stored in the second remote peer over second communications channel, and

manage the first and second communications channels via the first and second MDS peer instances, respectively.

18. The system of claim 17, wherein the peer manager is configured to maintain a plurality of communications channels via a corresponding one of local MDS peer instances for exchanging metadata with a plurality of remote peers, respectively.

19. The system of claim 18, wherein the peer manager is configured to:

receive a first signal from the first remote peer indicating that the first communications channel is no longer needed; and

in response to the first signal, destroy the first local MDS peer instance to shut down the first communications channel.

20. The system of claim 18, wherein the peer manager is configured to:

receive a second signal from the local client indicating that the second communications channel is no longer needed; and

in response to the second signal, destroy the second local MDS peer instance to shut down the second communications channel.

21. The system of claim 17, wherein the first local MDS peer instance is configured to operate as an MDS server with respect to the first remote MDS peer instance.

22. The system of claim 21, wherein the second local MDS peer instance is configured to operate as an MDS client with respect to the second remote MDS peer instance.

23. The system of claim 17, wherein creating and initiating the first local MDS peer instance comprises:

authenticating a first user of the first remote peer based on a first user credential of the first user received from the first remote peer;

transmitting to the first remote peer a first MDS channel token representing an access permission to a first storage volume associated with the local peer that stores the requested metadata; and

providing the first user of the first remote peer access of the first storage volume based on the first MDS channel token.

24. The system of claim 17, wherein creating and initiating the second local MDS peer instance comprises:

transmitting a second user credential of a second user of the local client to the second remote peer to allow the second remote peer to authenticate the second user;

receiving from the second remote peer a second MDS channel token representing an access permission to a second storage volume associated with the second remote peer; and

providing the second user access of the second storage volume of the second remote peer based on the second MDS channel token.