Panic occured while committing writer with sort by text field. about tantivy HOT 6 OPEN

sort by is only supported on numerical fields. Why do you want to sort by text field?

from tantivy.

sort by is only supported on numerical fields. Why do you want to sort by text field?

Because my source data is from MongoDB. Its id field is ObjectId type, and there is no way to store ObjectId type as a number to tantivy. Therefore, I use text to store the id field. For keeping the order, I would like to sort by the id field with text type.

from tantivy.

I suggest we just remove the ability to sort the index by something. It has brought more bugs, confusion than any other feature.

from tantivy.

Because tantivy has its own docId field, and tantivy's interface does not provide a save method (override by query). This leads to the confusion of query results in concurrent testing (single-threaded modification + multithreaded query). So, I think index sort is necessary.

from tantivy.

I don't understand your sentence.

from tantivy.

For keeping the order, I would like to sort by the id field with text type.

Why do you want to keep order in the tantivy index?

I suggest we just remove the ability to sort the index by something. It has brought more bugs, confusion than any other feature.

I also don't think the maintenance cost of it justifies potential gains currently. In practice there's little to no benefit, but some confusion about it.
Range queries may be accelerated by using binary search instead of a full scan, but we don't do that currently.
Compression may be improved, we don't have much data about that though.

Tantivy users may have custom queries on top of sorting. Hard to tell if and how they use it, but only performance should be affected when removing it.

If we decide to remove it I would add a deprecation warning in the upcoming release.

from tantivy.