Toke Eskildsen

Aren't geo-coordinates floats? That would work for a partial benchmark, but would not hit the variable bits per value-packing used by whole numbers in the Lucene70DocValues codec. I wrote the...

Sorting is a fine test for checking for regression. For random access impact measurement it is poor as it extracts the values sequentially with skip-ahead: The skip-cache only activates when...

Do you consider Solr's `export` to be abuse? It requires doc values for delivering the result and is highly affected by the switch to iterative DVs. I hadn't experimented with...

We seem to have a bit of radio silence, @jpountz . Maybe I could persuade you to signal if you have lost interest in this issue or if you just...

I am not very familiar with the internal workings of `export`, so I don't know why it uses `advance`. Could be it is just an oversight? Regarding my example, there...

@dsmiley Do you find it to be irrelevant if changes to the Lucene codec leads to performance regressions in Solr `export`?

Avoiding going further into the debate about what this part of the software is for, let me try and take a step back. The change to an iterative API for...

> Right they should all follow the same pattern: iterate over hits of the query and do something with the value, so it shouldn't matter. Okay, we're getting somewhere now....

FYI: I am currently busy with in-house work. I'll get back to the current issue later. Regarding the abuse thing, I have posted "DocValues, retrieval performance and policy" on the...

> I believe solr and lucene is unlikely to support anything longer than 128 bits - The underlying implementation types only support a maximum of 128 bits. The underlying implementation...