Hrmph. I've got an Ant based codebase for building custom components
against Solr. I've been asked on numerous occasions to publish this
codebase. It is now at:
https://github.com/upayavira/custom-solr-components
There's no sample code in there yet. I'll see if I can stick one in
there now, but I
Hi All,
Recently I have started to work on an new project. I found a collection where
there are few documents (~8000), but each document has only a big text field
with about 4/5 MB.
As far as I understood the text field is created by copying all the text fields
existing into a mssql table. So
Ask yourself what you want out of the index, how you want to query it,
then the way to structure your index will become more clear.
What sort of queries do you need to execute?
Upayavira
On Sat, Jan 2, 2016, at 01:30 PM, Vincenzo D'Amore wrote:
> Hi All,
>
> Recently I have started to work on a
Indexing the various columns of your database table as separate fields into
solr will allow for more flexibility in terms of filter queries, faceting
and sorting your results. If you're looking to implement such features then
you should definitely be indexing every table column as a separate solr
f
If you happen to be looking at "top" or the like, you
might be seeing virtual memory, see Uwe's
excellent blog here:
http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html
Best,
Erick
On Fri, Jan 1, 2016 at 11:46 PM, Shawn Heisey wrote:
> On 12/31/2015 8:03 PM, Zheng Lin Edwin Y
Yes we would like backward compatibility. We cannot switch all the facet
fields to DocValues and our faceting is slow.
Please...
On Fri, Jan 1, 2016 at 7:41 AM, Jamie Johnson wrote:
> Is there any interest in this? While i think it's important and inline
> with faceting available in the new js
