How to store a HashSet in the index?

Hi, Can anyone help me on, as to how I can go about efficiently indexing (actually, storing in the index) and retrieving, a HashSet object, which contains multiple string arrays? I just want to store the HashSet in the index, and not search on it. The HashSet should be returned with the document

[jira] Commented: (SOLR-303) Distributed Search over HTTP

[ https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549970 ] Sabyasachi Dalal commented on SOLR-303: --- I fixed the issue with the patch and it works with version 594268.

[jira] Commented: (SOLR-409) Allow configurable class loader sharing between cores

[ https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550002 ] Walter Ferrara commented on SOLR-409: - Thanks for committing this patch. I noticed that when you have just one

[jira] Commented: (SOLR-281) Search Components (plugins)

[ https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550031 ] Sabyasachi Dalal commented on SOLR-281: --- I am updating the distributed search patch (SOLR-303) with this patch.

Re: How to store a HashSet in the index?

On 10-Dec-07, at 12:09 AM, Rishabh Joshi wrote: Can anyone help me on, as to how I can go about efficiently indexing (actually, storing in the index) and retrieving, a HashSet object, which contains multiple string arrays? I just want to store the HashSet in the index, and not search on

[jira] Updated: (SOLR-415) LoggingFilter for debug

[ https://issues.apache.org/jira/browse/SOLR-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi updated SOLR-415: Attachment: SOLR-415.patch attached a revised patch as Hoss kindly suggested. LoggingFilter for

solrj for distributed search

I've been hacking on SOLR-303 (distributed search), and I started to write my own XML parsing code utilizing stax (streaming), when I realized that the code had already been written (in SolrJ). Should we use SolrJ for making and parsing the distributed search requests? One downside is that SolrJ

Re: Confluence wiki vs MoinMoin

: What is really missing is that we don't (at least I don't) have a clear sense : where what type of docs should go. Some in javadocs, some on the wiki, almost : none on the forrest site. Javadocs work great since they are attached to : sources and get included in releases. But solr's users

Re: solrj for distributed search

I think (re)using solrj is a good idea. As a client, I'd rather have one API to use for both distributed and non-distributed calls to Solr. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message From: Yonik Seeley [EMAIL PROTECTED] To:

purpose of MultiCore default ?

Forgive me if i'm off base with some stuff here ... i'm still trying to wrap my head arround some of the new multicore stuff. Ryan's comments in SOLR-428 have made me realize that the default core means more then i thought. I had missunderstood it to be a way of specifying what the legacy

multicore and admin pages?

I notice this in the MultiCore wiki... To access the admin pages for each core visit: http://localhost:8983/solr/admin/?core=core0 http://localhost:8983/solr/admin/?core=core1 ...trying this out using the example multicore setup didn't seem to work (the admin screen said core0 even