Hi, Thanks for all the comments.
Yes, I agree with everyone, Solr seems too much for now, and Lucene will easily fill our requirements for search. So I will stick with just Lucene for now, and maybe, in future, we could switch to Solr, I think no interface changes would be necessary for that. Best Regards, Phillipe Ramalho On Wed, May 26, 2010 at 1:26 AM, Suhothayan Sriskandarajah < [email protected]> wrote: > Hi > > Good idea, It would be easy to implement and maintain. > But as Others mentioned if we are only using the functionalities that could > be anyway achieved by Lucene, > and if we don't have a real need to go with Solr. > I think Lucene will be OK since Solr has too many dependencies. > > Thoughts ? > > suho > > > On 26 May 2010 01:11, Adriano Crestani <[email protected]> wrote: > > > Hi Phillipe, > > > > It's a good idea, Solr would be much easier to maintain. However, I think > > Advhesh made a point, Solr has too many dependencies, and I think we > won't > > use most of them, only Solr war file (no plugins included) has 4.1M and > the > > latest lucene-core jar has only 1M. > > > > If I got it right, all you need to do is pick the right Analyzer and use > it > > with Lucene, you won't spend much time writing any new > > Analyzer/Tokenizer/TokenFilter, so implementing a search component only > > with > > Lucene should be straightforward :) > > > > Adriano Crestani > > > > On Tue, May 25, 2010 at 1:13 PM, Henry Saputra <[email protected] > > >wrote: > > > > > Solr is basically part of Apache Lucene project, I think you meant the > > > Lucene Java core. > > > > > > So your idea is to make Solr as separate web application that Photark > > could > > > talk to via REST endpoints? > > > > > > I think Solr is a bit too much for tagging and search features in > > PhotArk. > > > > > > I could just create PhotArk search component that warp/extend Lucene > core > > > Java functionalities to point to internal indexing logic. > > > > > > Just my 2 cents. > > > > > > - Henry > > > > > > On Tue, May 25, 2010 at 12:42 AM, Phillipe Ramalho < > > > [email protected]> wrote: > > > > > > > Hi, > > > > > > > > I have been considering to use Solr, instead of using Lucene, to > > > implement > > > > the search functionality for Photark. > > > > > > > > From solr website: "Solr is a standalone enterprise search server > with > > a > > > > web-services like API. You put documents in it (called "indexing") > via > > > XML > > > > over HTTP. You query it via HTTP GET and receive XML results. " [1] > > > > > > > > Solr uses Lucene as search engine and adds a bunch of features on top > > of > > > > it, > > > > as "Comprehensive HTML Administration Interfaces", "Flexible and > > > Adaptable > > > > with XML configuration" and "Standards Based Open Interfaces - > XML,JSON > > > and > > > > HTTP ". So, most of configuration would be done via admin html > > interfaces > > > > and xml files, making it easier for Photark users to change the > default > > > > Photark search configuration if they want to. > > > > > > > > My idea is to expose Solr as SCA component, and it will be consumed > by > > > > PhotarkSearchComponent, which will receive add/update/remove photo > > events > > > > from the main Photark component, extract searchable info from the > Image > > > > objects and push it to SolrComponent. To search, the user could > > directly > > > > call SolrComponent. > > > > > > > > Comments? :) > > > > > > > > Regards, > > > > Phillipe Ramalho > > > > > > > > [1] - http://lucene.apache.org/solr/features.html > > > > > > > > > > -- Phillipe Ramalho
