Greetings Comrades.
There were numerous requests and considerations on using Solr as both
search engine and NoSQL store at the same time.
While being an excellent tool as a search engine, Solr is looking not so
good when it comes to storing documents and various stored fields,
especially with big a
November 2014 08:52, andrey prokopenko wrote:
> > I assume, there might be other developers, trying to solve similar
> > problems, so I'd be interested to hear about similar attempts & issues
> > encountered while trying to implement such an integration between Solr
>
I echo that. Atomic update is merely a decoration over the same
delete/insert pattern, where Solr processor inplace retrieves all the
stored fields of the the document, updates the field, then checks _version_
field prior to update and if it was correct, deletes, then insert new
version of the docu
With "out of the box" functionality, no. You have to develop custom
UpdateProcessor and add it to the updateprocessors chain.
On Thu, Nov 6, 2014 at 3:19 PM, yriveiro wrote:
> Hi,
>
> It's possible remove store data of an index deleting the unwanted fields
> from schema.xml and after do an optim
SolrCoud cluster heavily depends on data locality and high I/O, thus any
NFS with access to disk array over the network is multitude times slower
than direct I/O and must be avoided. Classical JBOD (just a bunch of disks)
config + memory mapped files ensure high performance.
On Wed, Nov 5, 2014 at
; On Fri, Nov 7, 2014 at 10:39 AM, andrey prokopenko
> wrote:
>
> > With "out of the box" functionality, no. You have to develop custom
> > UpdateProcessor and add it to the updateprocessors chain.
> > On Thu, Nov 6, 2014 at 3:19 PM, yriveiro wrote:
> >
With omitTermFremFreqAndPositions set to true and multivalued field you
have no information how many times "zip" term or any other term has
appeared in the particular field. If the number of unique values is low,
you can try faceting query with prefix, but it will not give you accurate
results due
t fields and is
> under the complete control of the developer.
>
> DataStax Enterprise also utilizes an indexing queue so that Cassandra
> inserts and updates can occur at full speed, with indexing in a background
> thread, maximizing ingestion performance.
>
> -- Jack Krupansky
&
