Re: Solritas in production

[george123 <da...@gmail.com>]

Apologies to drag this conversation up.

I want to share my experience.

Im a code hacker, I have written about 10 lines of code in my life, but can
figure out most things and how they work, or how to get them to work.

Im looking at deploying a vertical search engine. The data is a bit messy,
but im normalising it as best I can and solr just seems to handle it so
well. Who can argue with results in miliseconds.

Now, I need to develop a front end. This is proving THE most difficult part
of my solr experience.

My options are.
1. Defailt Solritas/velocity
2. Wrap this into a drupal or similar cms with solr functionality.
3. Code this in php.

I dont have the knowledge to code in php. I cant use a cms for a variety of
reasons, most of which are related to how it is handled in the database and
the format of my data not fitting to a cms's framework, so im left to look
at point 1 again.

Im sure the knowledge in this forum is without question, but when I see
things like "not production ready" that doesnt mean much to me, someone
hacking out a website. Im bootstrapping so finding someone to code an option
3 for me is a bit hard, even with offshore freelance help.

If there was a set of steps to get Velocity working with my system that
would give me a solution. Alternatively, if the php (or other) code clients
coded a basic frontend template that guys like me could hack out that would
open up the solr framework to a wider range of people.

Anyway, after reading this post, and the one on this blog
http://thoughtsasaservice.wordpress.com/2012/05/10/should-you-use-solritas-on-production/
I think I am going to look down the path of this further. 

The biggest drawback to this I can see is that Velocity consumes more
memory, for me in my situation thats actually ok. Using host side tools like
apache httpd or varnish as has been suggested is something that is possible
in my situation - but a bolt on solution would be ideal. 

Hopefully my experience helps others. I wonder how many people like me
(wordpress/joomla template hackers at best) go to the apache solr project
and turn away because they cant figure out aspects, or they cant just
install a simple solution.

Dont dump velocity, it ticks so many boxes. Please add to it!



--
View this message in context: http://lucene.472066.n3.nabble.com/Solritas-in-production-tp3966191p4000661.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solritas in production

[Erick Erickson <er...@gmail.com>]

Just make really, really sure you don't allow queries like:
.../solr/update?stream.body=<delete><query>*:*</query></delete>

Best
Erick

On Sun, Aug 12, 2012 at 8:42 AM, george123 <da...@gmail.com> wrote:
> Apologies to drag this conversation up.
>
> I want to share my experience.
>
> Im a code hacker, I have written about 10 lines of code in my life, but can
> figure out most things and how they work, or how to get them to work.
>
> Im looking at deploying a vertical search engine. The data is a bit messy,
> but im normalising it as best I can and solr just seems to handle it so
> well. Who can argue with results in miliseconds.
>
> Now, I need to develop a front end. This is proving THE most difficult part
> of my solr experience.
>
> My options are.
> 1. Defailt Solritas/velocity
> 2. Wrap this into a drupal or similar cms with solr functionality.
> 3. Code this in php.
>
> I dont have the knowledge to code in php. I cant use a cms for a variety of
> reasons, most of which are related to how it is handled in the database and
> the format of my data not fitting to a cms's framework, so im left to look
> at point 1 again.
>
> Im sure the knowledge in this forum is without question, but when I see
> things like "not production ready" that doesnt mean much to me, someone
> hacking out a website. Im bootstrapping so finding someone to code an option
> 3 for me is a bit hard, even with offshore freelance help.
>
> If there was a set of steps to get Velocity working with my system that
> would give me a solution. Alternatively, if the php (or other) code clients
> coded a basic frontend template that guys like me could hack out that would
> open up the solr framework to a wider range of people.
>
> Anyway, after reading this post, and the one on this blog
> http://thoughtsasaservice.wordpress.com/2012/05/10/should-you-use-solritas-on-production/
> I think I am going to look down the path of this further.
>
> The biggest drawback to this I can see is that Velocity consumes more
> memory, for me in my situation thats actually ok. Using host side tools like
> apache httpd or varnish as has been suggested is something that is possible
> in my situation - but a bolt on solution would be ideal.
>
> Hopefully my experience helps others. I wonder how many people like me
> (wordpress/joomla template hackers at best) go to the apache solr project
> and turn away because they cant figure out aspects, or they cant just
> install a simple solution.
>
> Dont dump velocity, it ticks so many boxes. Please add to it!
>
>
>
> --
> View this message in context: http://lucene.472066.n3.nabble.com/Solritas-in-production-tp3966191p4000661.html
> Sent from the Solr - User mailing list archive at Nabble.com.