All in all is there anything that we can say before measuring the
performance comparison of storing the stored values of documents at Hbase?
I mean as like:
* I will need to communicate with Hbase and this will produce more latency
than Lucene
* I will loose some built-in functionality that integr
Any rule of thumb regarding the size of document limitation when storing it
in solr?
Otis Gospodnetic-5 wrote
> Use Solr. It's pretty clear you don't yet have any problems that
> would make you think about alternatives. Using Solr to store and not
> just index will make your life simpler (and
Use Solr. It's pretty clear you don't yet have any problems that
would make you think about alternatives. Using Solr to store and not
just index will make your life simpler (and your app simpler and
likely faster).
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Tue, Apr 16, 20
Thanks again for your answer. If I find any document about such comparisons
that I would like to read.
By the way, is there any advantage for using Lucene instead of anything
else as like that:
Using Lucene is naturally supported at Solr and if I use anything else I
may face with some compatibili
People do use other data stores to retrieve data sometimes. e.g. Mongo
is popular for that. Like I hinted in another email, I wouldn't
necessarily recommend this for common cases. Don't do it unless you
really know you need it. Otherwise, just store in Solr.
Otis
--
Solr & ElasticSearch Support
Hi Otis and Jack;
I have made a research about highlights and debugged code. I see that
highlight are query dependent and not stored. Why Solr uses Lucene for
storing text, I mean i.e. content of a web page. Is there any comparison
about to store texts at Hbase or any other databases versus Lucene
Source code is your best bet. Wiki has info about how to use it, but
not how highlighting is implemented. But you don't need to understand
the implementation details to understand that they are dynamic,
computed specifically for each query for each matching document, so
you cannot store them anyw
Hi Otis;
It seems that I should read more about highlights. Is there any where that
explains in detail how highlights are generated at Solr?
2013/4/11 Otis Gospodnetic
> Hi,
>
> You can't store highlights ahead of time because they are query
> dependent. You could store documents in HBase and
Hi,
You can't store highlights ahead of time because they are query
dependent. You could store documents in HBase and use Solr just for
indexing. Is that what you want to do? If so, a custom
SearchComponent executed after QueryComponent could fetch data from
external store like HBase. I'm not
Actually I don't think to store documents at Solr. I want to store just
highlights (snippets) at Hbase and I want to retrieve them from Hbase when
needed.
What do you think about separating just highlights from Solr and storing
them into Hbase at Solrclod. By the way if you explain at which process
You may also be interested in looking at things like solrbase (on Github).
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Sat, Apr 6, 2013 at 6:01 PM, Furkan KAMACI wrote:
> Hi;
>
> First of all should mention that I am new to Solr and making a research
> about it. What I am tr
Solr would not be storing the original source form of the documents in any
case. Whether you use Tika or SolrCell, only the text stream of the content
and the metadata would ever get indexed or stored in Solr.
Solr completely decouples "indexing" and "storing" of data values. If you
don't want
12 matches
Mail list logo
