You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, in Bluge we removed the DocIDQuery because we want to emphasize that there isn't really anything special about the _id field. It is just a field in which all values are unique. To search for a document using it's identifier, you should simply create a term query for the ID, and scope it to only search the _id field.
Background: The top-level Bluge API makes it easy to create documents, all which have a field named _id, and we do this because it works well for many use cases. However, the internals of Bluge were designed to not assume/require this field. Also, one of the design constraints of Bluge was to have a smaller API surface area where possible (avoid multiple ways to do the same thing). Given both of these, it made sense to me to remove it. In summary I would say that we want Bluge developers to not think of ID's as special, and instead think of them like just another field.
Bleve used to have a DocIDQuery, Is that not built on purpose in bluge. What is the recommendation for querying a specific document by DocID?
The text was updated successfully, but these errors were encountered: