You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Mark <st...@gmail.com> on 2011/04/07 21:43:44 UTC

Lucid Works

I noticed that Lucid Works distribution now says is upt to date with 4.X 
versions. Does this mean 1.4 or 4.0/trunk?

If its truly 4.0 does that mean it includes the collapse component? 
Also, is the click scoring tools proprietary or was this just a 
contrib/patch that was applied?

Thanks

Re: Lucid Works

Posted by Lance Norskog <go...@gmail.com>.
Just to be clear, we are talking about two different Lucid Imagination products.

The Certified Distribution is a repackaging of the public Solr
releases with various add-on goodies that Lucid and others have
written over the years. This is the "drop-in replacement" for the
Apache release of Solr.

LucidWorks is a commercial product with a free download for
developers. LucidWorks has a core server and an external Ruby-based
UI.

On Fri, Apr 8, 2011 at 3:14 PM, Erik Hatcher <er...@gmail.com> wrote:
>
> On Apr 8, 2011, at 17:32 , Mark wrote:
>
>> How come this new version is bundled with rails and why is there no .war output format?
>
> Rails, via JRuby, is used in LucidWorks Enterprise for both the admin and search interfaces. (and also powers the Alerts REST API).
>
>> I wanted a simple drop in replacement for my current war :(
>
> LucidWorks Enterprise is a standalone install, and intentionally controls the full environment (using Jetty).  While it *is* Solr, it is also a lot more around it and a product we are supporting thoroughly.   It's better for us, and our customers, to have as controlled an environment as possible.
>
> As a search engine user, especially with LucidWorks Enterprise, the idea is to speak an API to it (a REST control API, as well as standard Solr HTTP interface)... making dropping in newer versions relatively straightforward.
>
> [an aside, there are plans to release a LucidWorks for Solr 3.1/.x certified distribution too - I can't speak to the timeline of such a release though]
>
>        Erik
>
>



-- 
Lance Norskog
goksron@gmail.com

Re: Lucid Works

Posted by Erik Hatcher <er...@gmail.com>.
On Apr 8, 2011, at 17:32 , Mark wrote:

> How come this new version is bundled with rails and why is there no .war output format?

Rails, via JRuby, is used in LucidWorks Enterprise for both the admin and search interfaces. (and also powers the Alerts REST API).

> I wanted a simple drop in replacement for my current war :(

LucidWorks Enterprise is a standalone install, and intentionally controls the full environment (using Jetty).  While it *is* Solr, it is also a lot more around it and a product we are supporting thoroughly.   It's better for us, and our customers, to have as controlled an environment as possible.

As a search engine user, especially with LucidWorks Enterprise, the idea is to speak an API to it (a REST control API, as well as standard Solr HTTP interface)... making dropping in newer versions relatively straightforward.  

[an aside, there are plans to release a LucidWorks for Solr 3.1/.x certified distribution too - I can't speak to the timeline of such a release though]

	Erik


Re: Lucid Works

Posted by Mark <st...@gmail.com>.
How come this new version is bundled with rails and why is there no .war 
output format?

I wanted a simple drop in replacement for my current war :(

On 4/8/11 1:27 PM, Andrzej Bialecki wrote:
> On 4/8/11 9:55 PM, Andy wrote:
>>
>> --- On Fri, 4/8/11, Andrzej Bialecki<ab...@getopt.org>  wrote:
>>
>>
>>> :) If you don't need the new functionality in 4.x, you don't
>>> need the performance improvements,
>>
>> What performance improvements does 4.x have over 3.1?
>
> Ah... well, many - take a look at the CHANGES.txt.
>
>>
>>> reindexing cycles are long (indexes tend to stay around)
>>> then 3.1 is a safer bet. If you need a dozen or so new
>>> exciting features (e.g. results grouping) or top
>>> performance, or if you need LucidWorks with Click and other
>>> goodies, then use 4.x and be prepared for an occasional full
>>> reindex.
>>
>> So using 4.x would require occasional full reindex but using 3.1 
>> would not? Could you explain? I thought 4.x comes with NRT indexing. 
>> So why is full reindex necessary?
>
> Well, so long as you don't want to upgrade then of course, index 
> format is stable and you can manage it incrementally. But in case of 
> an upgrade, because in 4.x index format is not stable - if you upgrade 
> to a newer Lucene / LucidWorks of 4.x vintage then it may be the case 
> that even though indexes before and after upgrade are of 4.x vintage 
> they are still incompatible.
>
> At some point there may be tools to transparently convert indexes from 
> one 4.x to another 4.x format, but they are not there yet.
>

Re: Lucid Works

Posted by Andrzej Bialecki <ab...@getopt.org>.
On 4/8/11 9:55 PM, Andy wrote:
>
> --- On Fri, 4/8/11, Andrzej Bialecki<ab...@getopt.org>  wrote:
>
>
>> :) If you don't need the new functionality in 4.x, you don't
>> need the performance improvements,
>
> What performance improvements does 4.x have over 3.1?

Ah... well, many - take a look at the CHANGES.txt.

>
>> reindexing cycles are long (indexes tend to stay around)
>> then 3.1 is a safer bet. If you need a dozen or so new
>> exciting features (e.g. results grouping) or top
>> performance, or if you need LucidWorks with Click and other
>> goodies, then use 4.x and be prepared for an occasional full
>> reindex.
>
> So using 4.x would require occasional full reindex but using 3.1 would not? Could you explain? I thought 4.x comes with NRT indexing. So why is full reindex necessary?

Well, so long as you don't want to upgrade then of course, index format 
is stable and you can manage it incrementally. But in case of an 
upgrade, because in 4.x index format is not stable - if you upgrade to a 
newer Lucene / LucidWorks of 4.x vintage then it may be the case that 
even though indexes before and after upgrade are of 4.x vintage they are 
still incompatible.

At some point there may be tools to transparently convert indexes from 
one 4.x to another 4.x format, but they are not there yet.

-- 
Best regards,
Andrzej Bialecki     <><
  ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com


Re: Lucid Works

Posted by Andy <an...@yahoo.com>.
--- On Fri, 4/8/11, Andrzej Bialecki <ab...@getopt.org> wrote:


> :) If you don't need the new functionality in 4.x, you don't
> need the performance improvements, 

What performance improvements does 4.x have over 3.1?

> reindexing cycles are long (indexes tend to stay around)
> then 3.1 is a safer bet. If you need a dozen or so new
> exciting features (e.g. results grouping) or top
> performance, or if you need LucidWorks with Click and other
> goodies, then use 4.x and be prepared for an occasional full
> reindex.

So using 4.x would require occasional full reindex but using 3.1 would not? Could you explain? I thought 4.x comes with NRT indexing. So why is full reindex necessary?

Thanks.

Andy


Re: Lucid Works

Posted by Andrzej Bialecki <ab...@getopt.org>.
On 4/8/11 4:58 PM, Mark wrote:
> Doesn't look like you allow new members to post questions in that forum.

There's a "Create new account" link there, you simply need to register 
and log in.

>
> I have just one last question ;)
>
> We are deciding whether to upgrade our 1.4 production environment to 4.x
> or 3.1. What were you decisions when deciding to release 4.x over 3.1?

Based on the details that you provided I'd say "it depends" :) If you 
don't need the new functionality in 4.x, you don't need the performance 
improvements, and if your full reindexing cycles are long (indexes tend 
to stay around) then 3.1 is a safer bet. If you need a dozen or so new 
exciting features (e.g. results grouping) or top performance, or if you 
need LucidWorks with Click and other goodies, then use 4.x and be 
prepared for an occasional full reindex.

-- 
Best regards,
Andrzej Bialecki     <><
  ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com


Re: Lucid Works

Posted by Erick Erickson <er...@gmail.com>.
Unless you need the goodies in 4.x, I'd go with 3.1, just on the
principle that 4.x is more fluid than 3.1, and I'd go with more
static code. 4.x gets whatever patches the committers decide are good
whereas 3.1 (or 3.2 if that comes out) will have a smaller set of
changes.

Both are well tested, it's mostly a matter of your risk tolerance. Why
take any risk you don't have to?

Best
Erick

On Fri, Apr 8, 2011 at 10:58 AM, Mark <st...@gmail.com> wrote:

> Doesn't look like you allow new members to post questions in that forum.
>
> I have just one last question ;)
>
> We are deciding whether to upgrade our 1.4 production environment to 4.x or
> 3.1. What were you decisions when deciding to release 4.x over 3.1?
>
> Thanks again
>
>
> On 4/8/11 1:13 AM, Andrzej Bialecki wrote:
>
>> On 4/7/11 10:16 PM, Mark wrote:
>>
>>> Andrezej,
>>>
>>> Thanks for the info. I have a question regarding stability though. How
>>> are you able to guarantee the stability of this release when 4.0 is
>>> still a work in progress? I believe the last version Lucid released was
>>> 1.4 so why did you choose to release a 4.x version as opposed to 3.1?
>>>
>>
>> To include all the goodies from 4.0, of course ;) LucidWorks uses a
>> version from the trunk that behaves well in tests and with necessary patches
>> applied - see also below.
>>
>>
>>> Is the source code including with your distribution so that we may be
>>> able to do some further patching upon it?
>>>
>>
>> Yes, after installing it's in solr-src/ . So if any issue pops up you can
>> apply a patch, recompile the libs and replace them.
>>
>>
>>> Thanks again and hopefully I'll be joining you at that conference.
>>>
>>
>> Great :)
>>
>> PS. Questions like this are best asked on the Lucid forum
>> http://www.lucidimagination.com/forum/ .
>>
>>

Re: Lucid Works

Posted by Mark <st...@gmail.com>.
Doesn't look like you allow new members to post questions in that forum.

I have just one last question ;)

We are deciding whether to upgrade our 1.4 production environment to 4.x 
or 3.1. What were you decisions when deciding to release 4.x over 3.1?

Thanks again

On 4/8/11 1:13 AM, Andrzej Bialecki wrote:
> On 4/7/11 10:16 PM, Mark wrote:
>> Andrezej,
>>
>> Thanks for the info. I have a question regarding stability though. How
>> are you able to guarantee the stability of this release when 4.0 is
>> still a work in progress? I believe the last version Lucid released was
>> 1.4 so why did you choose to release a 4.x version as opposed to 3.1?
>
> To include all the goodies from 4.0, of course ;) LucidWorks uses a 
> version from the trunk that behaves well in tests and with necessary 
> patches applied - see also below.
>
>>
>> Is the source code including with your distribution so that we may be
>> able to do some further patching upon it?
>
> Yes, after installing it's in solr-src/ . So if any issue pops up you 
> can apply a patch, recompile the libs and replace them.
>
>>
>> Thanks again and hopefully I'll be joining you at that conference.
>
> Great :)
>
> PS. Questions like this are best asked on the Lucid forum 
> http://www.lucidimagination.com/forum/ .
>

Re: Lucid Works

Posted by Andrzej Bialecki <ab...@getopt.org>.
On 4/7/11 10:16 PM, Mark wrote:
> Andrezej,
>
> Thanks for the info. I have a question regarding stability though. How
> are you able to guarantee the stability of this release when 4.0 is
> still a work in progress? I believe the last version Lucid released was
> 1.4 so why did you choose to release a 4.x version as opposed to 3.1?

To include all the goodies from 4.0, of course ;) LucidWorks uses a 
version from the trunk that behaves well in tests and with necessary 
patches applied - see also below.

>
> Is the source code including with your distribution so that we may be
> able to do some further patching upon it?

Yes, after installing it's in solr-src/ . So if any issue pops up you 
can apply a patch, recompile the libs and replace them.

>
> Thanks again and hopefully I'll be joining you at that conference.

Great :)

PS. Questions like this are best asked on the Lucid forum 
http://www.lucidimagination.com/forum/ .

-- 
Best regards,
Andrzej Bialecki     <><
  ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com


Re: Lucid Works

Posted by Mark <st...@gmail.com>.
Andrezej,

Thanks for the info. I have a question regarding stability though. How 
are you able to guarantee the stability of this release when 4.0 is 
still a work in progress? I believe the last version Lucid released was 
1.4 so why did you choose to release a 4.x version as opposed to 3.1?

Is the source code including with your distribution so that we may be 
able to do some further patching upon it?

Thanks again and hopefully I'll be joining you at that conference.

On 4/7/11 12:54 PM, Andrzej Bialecki wrote:
> On 4/7/11 9:43 PM, Mark wrote:
>> I noticed that Lucid Works distribution now says is upt to date with 4.X
>> versions. Does this mean 1.4 or 4.0/trunk?
>>
>> If its truly 4.0 does that mean it includes the collapse component?
>
> Yes it does.
>
>> Also, is the click scoring tools proprietary or was this just a
>> contrib/patch that was applied?
>
> At the moment it's proprietary. I will have a talk at the Lucene 
> Revolution conference that describes the Click tools in detail.
>

Re: Lucid Works

Posted by Andrzej Bialecki <ab...@getopt.org>.
On 4/7/11 9:43 PM, Mark wrote:
> I noticed that Lucid Works distribution now says is upt to date with 4.X
> versions. Does this mean 1.4 or 4.0/trunk?
>
> If its truly 4.0 does that mean it includes the collapse component?

Yes it does.

> Also, is the click scoring tools proprietary or was this just a
> contrib/patch that was applied?

At the moment it's proprietary. I will have a talk at the Lucene 
Revolution conference that describes the Click tools in detail.

-- 
Best regards,
Andrzej Bialecki     <><
  ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com