+1
On Thu, Aug 27, 2020 at 1:31 PM Jasonstack Zhao Yang
wrote:
>
> +1
>
> On Thu, 27 Aug 2020 at 04:52, Ekaterina Dimitrova
> wrote:
>
> > +1
> >
> > On Wed, 26 Aug 2020 at 16:48, Caleb Rackliffe
> > wrote:
> >
> > > +1
> > >
> > >
> > >
> > > On Wed, Aug 26, 2020, 3:45 PM Patrick McFadin
> >
> About space efficiency, one of the biggest drawback of SASI was the huge
space required for index structure when using CONTAINS logic because of the
decomposition of text columns into n-grams. Will SAI suffer from the same
issue in future iterations ?
SAI does not have specific ngram support atm
ould have been
> >done
> >already.
> >
> >Sorry if it's a fuzzy answer, but I haven't run down every technical angle
> >on the integration with C* yet. The idea was still very much in the
> >wouldn't it be very cool if this thing lived in Cassandra.
What's the advantage over Lucene?
On Wed, Apr 10, 2013 at 10:43 PM, Matt Stump wrote:
> Druid was our inspiration to layer bitmap indexes on top of Cassandra.
> Druid doesn't work for us because or data set is too large. We would need
> many hundreds of nodes just for the pre-processed data. Wh
vel Yaskevich wrote:
> Yeah, that is why I wrote "if possible" :) Also, does FST provide a
> predecessor lookup function, wasn't clear from the blog post?
>
> On Friday 8 June 2012 at 22:53, Jason Rutherglen wrote:
>
> > Yeah that's fine, however if there isn&#
the main
> benefit from that trie could be O(log log M) predecessor lookup and compact
> in-memory size.
>
> [1] https://en.wikipedia.org/wiki/Y-fast_trie
>
> Best Regards
> --
> Pavel Yaskevich
>
>
> On Friday 8 June 2012 at 22:19, Jason Rutherglen wrote:
>
Ok looks like the IndexSummary encapsulates everything, I can start with
hacking that.
On Fri, Jun 8, 2012 at 11:50 AM, Jason Rutherglen <
jason.rutherg...@gmail.com> wrote:
> The Cassandra integration is probably beyond the time I have available.
> If the locations in the code tha
The Cassandra integration is probably beyond the time I have available. If
the locations in the code that need to be rewritten to use the FST are
known, and a patch simply 'plugs-in' the FST, that would be much easier.
Eg, I don't know how Cassandra stores the current key index for example...
Bas
Jun 6, 2012 at 12:05 PM, Jonathan Ellis wrote:
> Implementation is in IndexSummary.java; the core is
>
> private final ArrayList positions;
> private final ArrayList keys;
>
> So no, nothing fancy like prefix compression.
>
> On Wed, Jun 6, 2012 at 11:00 AM, Jason Rut
"...benchmarks show it as being 2x more CPU-efficient than the
equivalent pure-Java implementation..."
https://issues.apache.org/jira/browse/HADOOP-7761
Now something is broken, I stopped my laptop while Maven was
downloading something!
---
Buildfile: /home/j/src/CASSANDRA-3147/build.xml
maven-ant-tasks-localrepo:
maven-ant-tasks-download:
maven-ant-tasks-i
I think it's 'ant generate-eclipse-files'? Maybe we should make it show up?
d. https://issues.apache.org/jira/browse/CASSANDRA-1902
>
> On Tue, Aug 2, 2011 at 11:24 PM, Jason Rutherglen
> wrote:
>> Cassandra 'compacts' the way Lucene 'merges' segments. One
>> interesting new feature built into Lucene is [1] which avoids loading
>>
Cassandra 'compacts' the way Lucene 'merges' segments. One
interesting new feature built into Lucene is [1] which avoids loading
the source files into the system IO cache on compaction / merge.
Perhaps Cassandra already has this feature?
1.
https://builds.apache.org/job/Lucene-trunk/javadoc/all
14 matches
Mail list logo
