Federated search of multiple sources with conflict resolution
Methods and apparatuses related to federated search of multiple sources with conflict resolution are disclosed. A method may comprise obtaining a set of data ontologies (e.g., types, properties, and links) associated with a plurality of heterogeneous data sources; receiving a selection of a graph comprising a plurality of graph nodes connected by one or more graph edges; and transforming the graph into one or more search queries across the plurality of heterogeneous data sources. A method may comprise obtaining a first data object as a result of executing a first search query across a plurality of heterogeneous data sources; resolving, based on one or more resolution rules, at least the first data object with a repository data object; deduplicating data associated with at least the first data object and the repository data object prior to storing the deduplicated data in a repository that has a particular data model.
1. A system comprising:
one or more processors;
a memory storing instructions which, when executed by the one or more processors, causes performance of:
automatically importing a plurality of changes to data in a plurality of data sources when the plurality of changes occur,
wherein a first change is to first data in a first data source of the plurality of data sources,
wherein a second change is to second data in a second data source, of the plurality of data sources, that is different than the first data source,
wherein importing the plurality of changes comprising receiving, for each change of the plurality of changes, a push notification which is generated in response to said each change;
in response to receiving a particular push notification that is associated with a particular change pertaining to a data object, (1) searching, based on one or more first search criteria, a repository for a repository data object associated with the particular change and (2) searching, based on one or more second search criteria, a data source for a data source data object associated with the particular change;
inferring a change in a vector clock of the data object based on the particular change, wherein a first vector clock entry assigned to the repository data object has a first value and a second vector clock entry assigned to the data source data object has a second value;
deconflicting the change in the vector clock based on data source rankings or repository rankings.
2. The system of claim 1 , wherein:
searching the repository comprises searching the repository storing an object-central data model or a cache of the repository for the repository data object comprising the particular change described by the push notification;
searching the data source comprises searching the plurality of data sources for a federated data object comprising the particular change described by the push notification;
inferring the change in the vector clock comprises determining that the first vector clock entry for the repository data object differs from the second vector clock entry for the federated data object.
3. The system of claim 1 , wherein deconflicting the change in the vector clock comprises:
determining, from the data source rankings or repository rankings, that the data source is more authoritative than the repository storing an object-central data model;
in response to determining that the data source is more authoritative than the repository, updating the repository data object stored in the repository with the particular change to the data object in the data source.
4. The system of claim 1 , wherein the plurality of data sources is a plurality of heterogeneous data sources, each of which comprising one or more caches associated with one or more repositories.
5. The system of claim 1 , wherein the particular push notification comprises a particular location of the particular change.
6. The system of claim 1 , wherein the particular push notification does not contain the particular change.
7. One or more non-transitory computer-readable media storing instructions which, when executed by one or more processors, causes performance of:
automatically importing a plurality of changes to data in a plurality of data sources when the plurality of changes occur,
wherein a first change is to first data in a first data source of the plurality of data sources,
wherein a second change is to second data in a second data source, of the plurality of data sources, that is different than the first data source,
wherein importing the plurality of changes comprising receiving, for each change of the plurality of changes, a push notification which is generated in response to said each change;
in response to receiving a particular push notification that is associated with a particular change pertaining to a data object, (1) searching, based on one or more first search criteria, a repository for a repository data object associated with the particular change and (2) searching, based on one or more second search criteria, a data source for a data source data object associated with the particular change;
inferring a change in a vector clock of the data object based on the particular change, wherein a first vector clock entry assigned to the repository data object has a first value and a second vector clock entry assigned to the data source data object has a second value;
deconflicting the change in the vector clock based on data source rankings or repository rankings.
8. The one or more non-transitory computer-readable media of claim 7 , wherein:
searching the repository comprises searching the repository storing an object-central data model or a cache of the repository for the repository data object comprising the particular change described by the push notification;
searching the data source comprises searching the plurality of data sources for a federated data object comprising the particular change described by the push notification;
inferring the change in the vector clock comprises determining that the first vector clock entry for the repository data object differs from the second vector clock entry for the federated data object.
9. The one or more non-transitory computer-readable media of claim 7 , wherein deconflicting the change in the vector clock comprises:
determining, from the data source rankings or repository rankings, that the data source is more authoritative than the repository storing an object-central data model;
in response to determining that the data source is more authoritative than the repository, updating the repository data object stored in the repository with the particular change to the data object in the data source.
10. The one or more non-transitory computer-readable media of claim 7 , wherein the plurality of data sources comprises a plurality of heterogeneous data sources, each of which comprising one or more caches associated with one or more repositories.
11. The one or more non-transitory computer-readable media of claim 7 , wherein the particular push notification comprises a particular location of the particular change.
12. The one or more non-transitory computer-readable media of claim 7 , wherein the particular push notification does not contain the particular change.
13. A method comprising:
automatically importing a plurality of changes to data in a plurality of data sources when the plurality of changes occur,
wherein a first change is to first data in a first data source of the plurality of data sources,
wherein a second change is to second data in a second data source, of the plurality of data sources, that is different than the first data source,
wherein importing the plurality of changes comprising receiving, for each change of the plurality of changes, a push notification which is generated in response to said each change;
in response to receiving a particular push notification that is associated with a particular change pertaining to a data object, (1) searching, based on one or more first search criteria, a repository for a repository data object associated with the particular change and (2) searching, based on one or more second search criteria, a data source for a data source data object associated with the particular change;
inferring a change in a vector clock of the data object based on the particular change, wherein a first vector clock entry assigned to the repository data object has a first value and a second vector clock entry assigned to the data source data object has a second value;
deconflicting the change in the vector clock based on data source rankings or repository rankings.
14. The method of claim 13 , wherein:
searching the repository comprises searching the repository storing an object-central data model or a cache of the repository for the repository data object comprising the particular change described by the push notification;
searching the data source comprises searching the plurality of data sources for a federated data object comprising the particular change described by the push notification;
inferring the change in the vector clock comprises determining that the first vector clock entry for the repository data object differs from the second vector clock entry for the federated data object.
15. The method of claim 13 , wherein deconflicting the change in the vector clock comprises:
determining, from the data source rankings or repository rankings, that the data source is more authoritative than the repository storing an object-central data model;
in response to determining that the data source is more authoritative than the repository, updating the repository data object stored in the repository with the particular change to the data object in the data source.
16. The method of claim 13 , wherein the plurality of data sources comprises a plurality of heterogeneous data sources, each of which comprising one or more caches associated with one or more repositories.
17. The method of claim 13 , wherein the particular push notification comprises a particular location of the particular change.
18. The method of claim 13 , wherein the particular push notification does not contain the particular change.