Re: Returning to Solr 4.0 from 4.1

2013-03-03 Thread Dotan Cohen
On Sat, Mar 2, 2013 at 9:32 PM, Upayavira wrote: > What I'm questioning is whether the issue you see in 4.1 has been > resolved in Subversion. While I would not expect 4.0 to read a 4.1 > index, the SVN branch/4.2 should be able to do so effortlessly. > > Upayavira > I see, thanks. Actually, runn

Re: Returning to Solr 4.0 from 4.1

2013-03-02 Thread Upayavira
What I'm questioning is whether the issue you see in 4.1 has been resolved in Subversion. While I would not expect 4.0 to read a 4.1 index, the SVN branch/4.2 should be able to do so effortlessly. Upayavira On Sat, Mar 2, 2013, at 06:17 PM, Dotan Cohen wrote: > On Fri, Mar 1, 2013 at 1:37 PM, Upa

Re: Returning to Solr 4.0 from 4.1

2013-03-02 Thread Dotan Cohen
On Fri, Mar 1, 2013 at 1:37 PM, Upayavira wrote: > Can you use a checkout from SVN? Does that resolve your issues? That is > what will become 4.2 when it is released soon: > > https://svn.apache.org/repos/asf/lucene/dev/branches/branch_4x/ > > Upayavira > Thank you. Which feature of 4.2 are you s

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Lance Norskog
Yes, the SolrEntityProcessor can be used for this. If you stored the original document bodies in the Solr index! You can also download the documents in Json or CSV format and re-upload those to old Solr. I don't know if CSV will work for your docs. If CSV works, you can directly upload what you

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Alexandre Rafalovitch
What about SolrEntityProcessor in DIH? https://wiki.apache.org/solr/DataImportHandler#SolrEntityProcessor Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Upayavira
Can you use a checkout from SVN? Does that resolve your issues? That is what will become 4.2 when it is released soon: https://svn.apache.org/repos/asf/lucene/dev/branches/branch_4x/ Upayavira On Fri, Mar 1, 2013, at 10:51 AM, Dotan Cohen wrote: > On Fri, Mar 1, 2013 at 12:22 PM, Rafał Kuć wrot

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Dotan Cohen
On Fri, Mar 1, 2013 at 12:22 PM, Rafał Kuć wrote: > Hello! > > As far as I know you have to re-index using external tool. > Thank you Rafał. That is what I figured. -- Dotan Cohen http://gibberish.co.il http://what-is-what.com

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Rafał Kuć
Hello! As far as I know you have to re-index using external tool. -- Regards, Rafał Kuć Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch - ElasticSearch > On Fri, Mar 1, 2013 at 11:59 AM, Rafał Kuć wrote: >> Hello! >> >> I assumed that re-indexing can be painful in your case, if it

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Dotan Cohen
On Fri, Mar 1, 2013 at 11:59 AM, Rafał Kuć wrote: > Hello! > > I assumed that re-indexing can be painful in your case, if it wouldn't > you probably would re-index by now :) I guess (didn't test it myself), > that you can create another collection inside your cluster, use the > old codec for Lucen

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Rafał Kuć
Hello! I assumed that re-indexing can be painful in your case, if it wouldn't you probably would re-index by now :) I guess (didn't test it myself), that you can create another collection inside your cluster, use the old codec for Lucene 4.0 (setting the version in solrconfig.xml should be enough)

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Dotan Cohen
On Fri, Mar 1, 2013 at 11:28 AM, Rafał Kuć wrote: > Hello! > > I suppose the only way to make this work will be reindexing the data. > Solr 4.1 uses Lucene 4.1 as you know, which introduced new default > codec with stored fields compression and this is one of the reasons > you can't read that inde

Re: Returning to Solr 4.0 from 4.1

2013-03-01 Thread Rafał Kuć
Hello! I suppose the only way to make this work will be reindexing the data. Solr 4.1 uses Lucene 4.1 as you know, which introduced new default codec with stored fields compression and this is one of the reasons you can't read that index with 4.0. -- Regards, Rafał Kuć Sematext :: http://semat