Your call, though from experience thus sounds like either two or no blog posts. I certainly have killed a bunch of good articles by waiting for perfection....:-) On 15/04/2014 7:01 pm, "Michael Sokolov" <msoko...@safaribooksonline.com> wrote:
> A blog post is a great idea, Alex! I think I should wait until I have a > complete end-to-end implementation done before I write about it though, > because I'd also like to include some tips about configuring the new > suggesters with Solr (the documentation on the wiki hasn't quite caught up > yet, I think), and I don't have that working as I'd like just yet. But I > will follow up with something soon; probably I will be able to share code > on a public repo. > > -Mike > > On 04/14/2014 10:01 PM, Alexandre Rafalovitch wrote: > >> Hi Mike, >> >> Glad I was able to help. Good note about the PoolingReuseStrategy, I >> did not think of that either. >> >> Is there a blog post or a GitHub repository coming with more details >> on that? Sounds like something others may benefit from as well. >> >> Regards, >> Alex. >> P.s. If you don't have your own blog, I'll be happy to host such >> article on mine. >> >> Personal website: http://www.outerthoughts.com/ >> Current project: http://www.solr-start.com/ - Accelerating your Solr >> proficiency >> >> >> On Tue, Apr 15, 2014 at 8:52 AM, Michael Sokolov >> <msoko...@safaribooksonline.com> wrote: >> >>> I lost the original thread; sorry for the new / repeated topic, but >>> thought >>> I would follow up to let y'all know that I ended up implementing Alex's >>> idea >>> to implement an UpdateRequestProcessor in order to apply different >>> analysis >>> to different fields when doing something analogous to copyFields. >>> >>> It was pretty straightforward except that when there are multiple >>> values, I >>> ended up needing multiple copies of the same Analyzer. I had to >>> implement a >>> new PoolingReuseStrategy for the Analyzer to handle this, which I hadn't >>> foreseen. >>> >>> -Mike >>> >> >
