bharath-techie commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2086176227
Thanks for the inputs @jpountz . Let me spend some more time on this.
But this is a topic which was thought of as well and one idea was to do
query abstraction / planni
jpountz commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2085447524
At first sight I don't like the fact that this seems to plug in a whole new
way of doing things. Either you don't use a star tree index and you do things
the usual way with filters
msokolov commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2085177581
My main concern was to ensure this exciting effort didn't get blocked by the
need to do major changes to existing indexing workloads. It sounds like the
plan here is less intrusive
bharath-techie commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2084365307
Thanks for the inputs @msokolov . I do see the similarities but the linked
issue seems to be tied to rollups done as part of merge aided by index sorting
on the dimensions. I
msokolov commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2083019231
This reminded me of an older issue:
https://github.com/apache/lucene/issues/11463 that seems to have foundered.
Maybe there is something to be learned from that, not sure.
--
Th
bharath-techie commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2082180161
Hi @jpountz ,
Good question, if we take `StarTreeDataCube` as an example implementation of
the above format :
We will traverse the `StarTree` and `StarTreeDocValues`
jpountz commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2081658301
It's not clear to me how we'd take advantage of this information at search
time. What changes would we make to e.g. `Collector` to allow it to take
advantage of these new data struc
bharath-techie commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2075553304
Thanks for the comments @msfroh .
Good idea, if we want to supply `Dims` and `metric` values to
`DataCubesWriter` as part of `addDocument` flow and consume them similar
msfroh commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2072834737
Wow! Adding data cube (OLAP) capabilities to Lucene could be really powerful.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
bharath-techie commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2068963512
### DataCubesFormat
```
public abstract class DataCubesFormat implements NamedSPILoader.NamedSPI {
/**
* Returns producer to read the data cube
bharath-techie commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2068945005
There are several advantages to keeping the new index as part of the same
Lucene segment. It reduces maintenance overhead and enables Near Real-Time
(NRT) use cases. Specific
msfroh commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2033117183
I wonder if we could think of this more broadly as a caching problem.
Basically, you could evaluate some "question" (aggregations, statistics,
etc.) for all segments and save t
jpountz commented on issue #13188:
URL: https://github.com/apache/lucene/issues/13188#issuecomment-2006649404
Figuring out the right API for this idea sounds challenging, but I like the
idea.
--
This is an automated message from the Apache Git Service.
To respond to the message, please lo
13 matches
Mail list logo
