Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A computerized search system, comprising: a search engine communicatively connected to a client device over a physical connection; a processor; and a storage unit coupled to the processor and storing a search index and instructions, wherein the instructions when translated by the processor cause the search engine to perform: when a capacity utilization of a partition in the search index is under a first threshold: allowing any object to be added to the partition; and allowing any existing object in the partition to be updated or deleted; when the capacity utilization of the partition is above the first threshold: disallowing any object to be added to the partition; and allowing any existing object in the partition to be updated or deleted; and when the capacity utilization of the partition is above a second threshold: disallowing any object to be added to the partition; allowing any existing object in the partition to be deleted; and moving any existing object in the partition that is subject to an update to another partition in the search index along with an indexing request.
A search system manages a search index by dividing it into partitions. Each partition has two capacity thresholds. Below the first threshold, the system allows adding new objects and updating/deleting existing ones. Above the first threshold, the system only allows updating/deleting existing objects, preventing new objects from being added. If a partition's capacity goes above the second threshold, new objects are still blocked, and updates to existing objects trigger the object (along with an indexing request) to be moved to another partition. The system connects to client devices over a physical connection.
2. The system of claim 1 , wherein the indexing request is generated by a partition manager based on the update associated with the existing object.
The search system described above includes a partition manager component. When an existing object in a partition exceeding the second capacity threshold needs to be updated, the partition manager generates an indexing request based on the update. This indexing request, along with the updated object, is then used to move the object to another partition, rebalancing the search index.
3. The system of claim 2 , wherein the moving is automatically and proactively performed by the partition manager when the capacity utilization of the partition is above the second threshold.
In the search system with the partition manager described above, when a partition's capacity goes above the second threshold, the partition manager automatically and proactively moves existing objects that are subject to an update to a different partition. This proactive rebalancing happens without waiting for a new indexing request.
4. The system of claim 2 , wherein the moving is performed by the partition manager in response to another indexing request received at the partition manager.
In the search system with the partition manager described above, the partition manager only moves an object to another partition when it receives a separate, new indexing request. Even if a partition's capacity is above the second threshold, the system waits for a new indexing request before moving the object.
5. The system of claim 1 , wherein the instructions when translated by the processor further cause the search engine to perform: changing from an Add mode to an Update mode when the capacity utilization of the partition meets or exceeds the first threshold; and changing from the Update mode to a Rebalancing mode when the capacity utilization of the partition meets or exceeds the second threshold.
The search system described above operates in different modes based on partition capacity. When a partition's utilization reaches the first threshold, the system switches from an "Add" mode (where new objects can be added) to an "Update" mode (where new object additions are blocked). When the utilization reaches the second threshold, the system switches from the "Update" mode to a "Rebalancing" mode, moving objects to other partitions upon update.
6. The system of claim 1 , wherein the instructions when translated by the processor further cause the search engine to perform: changing from an Update mode to an Add mode when the capacity utilization of the partition drops below the first threshold.
In the search system described above, the system switches from the "Update" mode back to the "Add" mode when a partition's capacity utilization drops below the first threshold. This allows the partition to accept new objects again.
7. The system of claim 1 , wherein the instructions when translated by the processor further cause the search engine to perform: changing from a Rebalancing mode to an Update mode when the capacity utilization of the partition drops below a third threshold.
In the search system described above, the system changes from the "Rebalancing" mode back to the "Update" mode when the capacity utilization of the partition drops below a third threshold. This third threshold is lower than the second threshold, effectively hysteresis.
8. A computer program product comprising at least one non-transitory computer readable medium storing instructions translatable by a processor, wherein the instructions when translated by the processor cause a search engine to perform: when a capacity utilization of a partition in a search index is under a first threshold: allowing any object to be added to the partition; and allowing any existing object in the partition to be updated or deleted; when the capacity utilization of the partition is above the first threshold: disallowing any object to be added to the partition; and allowing any existing object in the partition to be updated or deleted; and when the capacity utilization of the partition is above a second threshold: disallowing any object to be added to the partition; allowing any existing object in the partition to be deleted; and moving any existing object in the partition that is subject to an update to another partition in the search index along with an indexing request, the search index being connected to the search engine, the search engine being communicatively connected to a client device over a physical connection.
A computer program stored on a non-transitory medium manages a search index by dividing it into partitions. Each partition has two capacity thresholds. Below the first threshold, the program allows adding new objects and updating/deleting existing ones. Above the first threshold, the program only allows updating/deleting existing objects, preventing new objects from being added. If a partition's capacity goes above the second threshold, new objects are still blocked, and updates to existing objects trigger the object (along with an indexing request) to be moved to another partition. The search index connects to the search engine, which is connected to a client device.
9. The computer program product of claim 8 , wherein the indexing request is generated by a partition manager based on the update associated with the existing object.
The computer program described above includes a partition manager component. When an existing object in a partition exceeding the second capacity threshold needs to be updated, the partition manager generates an indexing request based on the update. This indexing request, along with the updated object, is then used to move the object to another partition, rebalancing the search index.
10. The computer program product of claim 9 , wherein the moving is automatically and proactively performed by the partition manager when the capacity utilization of the partition is above the second threshold.
In the computer program with the partition manager described above, when a partition's capacity goes above the second threshold, the partition manager automatically and proactively moves existing objects that are subject to an update to a different partition. This proactive rebalancing happens without waiting for a new indexing request.
11. The computer program product of claim 9 , wherein the moving is performed by the partition manager in response to another indexing request received at the partition manager.
In the computer program with the partition manager described above, the partition manager only moves an object to another partition when it receives a separate, new indexing request. Even if a partition's capacity is above the second threshold, the system waits for a new indexing request before moving the object.
12. The computer program product of claim 8 , wherein the instructions when translated by the processor further cause the search engine to perform: changing from an Add mode to an Update mode when the capacity utilization of the partition meets or exceeds the first threshold; and changing from the Update mode to a Rebalancing mode when the capacity utilization of the partition meets or exceeds the second threshold.
The computer program described above operates in different modes based on partition capacity. When a partition's utilization reaches the first threshold, the system switches from an "Add" mode (where new objects can be added) to an "Update" mode (where new object additions are blocked). When the utilization reaches the second threshold, the system switches from the "Update" mode to a "Rebalancing" mode, moving objects to other partitions upon update.
13. The computer program product of claim 8 , wherein the instructions when translated by the processor further cause the search engine to perform: changing from an Update mode to an Add mode when the capacity utilization of the partition drops below the first threshold.
In the computer program described above, the system switches from the "Update" mode back to the "Add" mode when a partition's capacity utilization drops below the first threshold. This allows the partition to accept new objects again.
14. The computer program product of claim 8 , wherein the instructions when translated by the processor further cause the search engine to perform: changing from a Rebalancing mode to an Update mode when the capacity utilization of the partition drops below a third threshold.
In the computer program described above, the system changes from the "Rebalancing" mode back to the "Update" mode when the capacity utilization of the partition drops below a third threshold. This third threshold is lower than the second threshold, effectively hysteresis.
15. A method for managing partitions in a computerized search system, the method performed by a search engine embodied on at least one non-transitory computer readable medium including instructions translable by a processor, the method comprising: when a capacity utilization of a partition in a search index is under a first threshold: allowing any object to be added to the partition; and allowing any existing object in the partition to be updated or deleted; when the capacity utilization of the partition is above the first threshold: disallowing any object to be added to the partition; and allowing any existing object in the partition to be updated or deleted; and when the capacity utilization of the partition is above a second threshold: disallowing any object to be added to the partition; allowing any existing object in the partition to be deleted; and moving any existing object in the partition that is subject to an update to another partition in the search index along with an indexing request, the search index being connected to the search engine, the search engine being communicatively connected to a client device over a physical connection.
A method for managing partitions in a search system comprises: dividing a search index into partitions, each with two capacity thresholds. Below the first threshold, the system allows adding new objects and updating/deleting existing ones. Above the first threshold, the system only allows updating/deleting existing objects, preventing new objects from being added. If a partition's capacity goes above the second threshold, new objects are still blocked, and updates to existing objects trigger the object (along with an indexing request) to be moved to another partition. The search index connects to the search engine, which is connected to a client device.
16. The method of claim 15 , wherein the indexing request is generated by a partition manager based on the update associated with the existing object.
The partition management method described above includes a partition manager component. When an existing object in a partition exceeding the second capacity threshold needs to be updated, the partition manager generates an indexing request based on the update. This indexing request, along with the updated object, is then used to move the object to another partition, rebalancing the search index.
17. The method of claim 16 , wherein the moving is automatically and proactively performed by the partition manager when the capacity utilization of the partition is above the second threshold.
In the partition management method with the partition manager described above, when a partition's capacity goes above the second threshold, the partition manager automatically and proactively moves existing objects that are subject to an update to a different partition. This proactive rebalancing happens without waiting for a new indexing request.
18. The method of claim 16 , wherein the moving is performed by the partition manager in response to another indexing request received at the partition manager.
In the partition management method with the partition manager described above, the partition manager only moves an object to another partition when it receives a separate, new indexing request. Even if a partition's capacity is above the second threshold, the system waits for a new indexing request before moving the object.
19. The method of claim 15 , further comprising: changing from an Add mode to an Update mode when the capacity utilization of the partition meets or exceeds the first threshold; and changing from the Update mode to a Rebalancing mode when the capacity utilization of the partition meets or exceeds the second threshold.
The partition management method described above includes operating in different modes based on partition capacity. When a partition's utilization reaches the first threshold, the system switches from an "Add" mode (where new objects can be added) to an "Update" mode (where new object additions are blocked). When the utilization reaches the second threshold, the system switches from the "Update" mode to a "Rebalancing" mode, moving objects to other partitions upon update.
20. The method of claim 15 , further comprising: changing from a Rebalancing mode to an Update mode when the capacity utilization of the partition drops below a third threshold.
The partition management method described above includes changing from the "Rebalancing" mode back to the "Update" mode when the capacity utilization of the partition drops below a third threshold. This third threshold is lower than the second threshold, effectively hysteresis.
Unknown
December 9, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.