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 Norberto Meijome <fr...@meijome.net> on 2008/08/18 04:03:41 UTC
DIH - commit / optimize
Hi again,
I see in the DIH wiki page :
[...]
full-import [..]
commit: (default 'true'). Tells whether to commit+optimize after the operation
[...]
but nothing for delta-import... I think it would be useful , a 'commit' (default=true) , 'optimize' (default=false) for the delta-import - these should most probably be separate ones, i think.
- for full-import , wouldn't it make sense to split commit + optimize into 2 different options? Granted, if I do a clean=true, i'd probably want (need!) an optimize... even then, optimize may be too slow / use too much memory at that point in time... ? ( not too sure about this argument..)
cheers,
B
_________________________
{Beto|Norberto|Numard} Meijome
Never take Life too seriously, no one gets out alive anyway.
I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.
Re: DIH - commit / optimize
Posted by Norberto Meijome <fr...@meijome.net>.
On Mon, 18 Aug 2008 10:14:32 +0800
"finy finy" <so...@gmail.com> wrote:
> i use solr for 3 months, and i find some question follow:
Please do not hijack mail threads.
http://en.wikipedia.org/wiki/Thread_hijacking
_________________________
{Beto|Norberto|Numard} Meijome
"Ask not what's inside your head, but what your head's inside of."
J. J. Gibson
I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.
Re: DIH - commit / optimize
Posted by finy finy <so...@gmail.com>.
i use solr for 3 months, and i find some question follow:
i check the solr source code, and find it uses lucene's QueryParser to parse
user's input querystring
for example, a query like this "name:ibmT63notebook" ,solr will parse it
like 'name:"ibm T63 notebook"' , it regard this as a PhrazeQuery,so it
will use PhrazeQuery.
but i want to get a result which include "ibm" and "T63" and "notebook" at
any postion. for example ,it should match some sentence like "i have a
notebook ,it is t63 of ibm"..
but solr doesn't do that,it consider that queryparser as a PhrazeQuery, how
can i do that as my mind?
thanks,
your friend!
Re: DIH - commit / optimize
Posted by Norberto Meijome <fr...@meijome.net>.
On Mon, 18 Aug 2008 09:34:56 +0530
"Shalin Shekhar Mangar" <sh...@gmail.com> wrote:
> Actually we have commit and optimize as separate request parameters
> defaulting to true for both full-import and delta-import. You can add a
> request parameter optimize=false for delta-import if you want to commit but
> not to optimize the index.
ah , now it makes perfect sense :) sorry, i should have checked the src myself.
thanks so much again :)
B
_________________________
{Beto|Norberto|Numard} Meijome
What you are afraid to do is a clear indicator of the next thing you need to do.
I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.
Re: DIH - commit / optimize
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
Please post the question as a separate mail with a new subject.
On Mon, Aug 18, 2008 at 9:58 AM, finy finy <so...@gmail.com> wrote:
> i'sorry, i am not familiar with the maillist operation.
> my question is:
>
> i check the solr source code, and find it uses lucene's QueryParser to parse
> user's input querystring
>
> for example, a query like this "name:ibmT63notebook" ,solr will parse it
> like 'name:"ibm T63 notebook"' , it regard this as a PhrazeQuery,so it
>
> will use PhrazeQuery.
>
> but i want to get a result which include "ibm" and "T63" and "notebook" at
> any postion. for example ,it should match some sentence like "i have a
> notebook ,it is t63 of ibm"..
>
> but solr doesn't do that,it consider that queryparser as a PhrazeQuery, how
> can i do that as my mind?
>
>
>
> 2008/8/18, Shalin Shekhar Mangar <sh...@gmail.com>:
>>
>> Actually we have commit and optimize as separate request parameters
>> defaulting to true for both full-import and delta-import. You can add a
>> request parameter optimize=false for delta-import if you want to commit but
>> not to optimize the index.
>>
>> I've updated the wiki. Thanks for pointing it out.
>>
>> On Mon, Aug 18, 2008 at 7:33 AM, Norberto Meijome <freebsd@meijome.net
>> >wrote:
>>
>> > Hi again,
>> >
>> > I see in the DIH wiki page :
>> > [...]
>> > full-import [..]
>> > commit: (default 'true'). Tells whether to commit+optimize after the
>> > operation
>> > [...]
>> >
>> > but nothing for delta-import... I think it would be useful , a 'commit'
>> > (default=true) , 'optimize' (default=false) for the delta-import - these
>> > should most probably be separate ones, i think.
>> >
>> > - for full-import , wouldn't it make sense to split commit + optimize
>> into
>> > 2 different options? Granted, if I do a clean=true, i'd probably want
>> > (need!) an optimize... even then, optimize may be too slow / use too much
>> > memory at that point in time... ? ( not too sure about this argument..)
>> >
>> > cheers,
>> > B
>> > _________________________
>> > {Beto|Norberto|Numard} Meijome
>> >
>> > Never take Life too seriously, no one gets out alive anyway.
>> >
>> > I speak for myself, not my employer. Contents may be hot. Slippery when
>> > wet. Reading disclaimers makes you go blind. Writing them is worse. You
>> have
>> > been Warned.
>> >
>>
>>
>>
>> --
>> Regards,
>> Shalin Shekhar Mangar.
>>
>
--
--Noble Paul
Re: DIH - commit / optimize
Posted by finy finy <so...@gmail.com>.
i'sorry, i am not familiar with the maillist operation.
my question is:
i check the solr source code, and find it uses lucene's QueryParser to parse
user's input querystring
for example, a query like this "name:ibmT63notebook" ,solr will parse it
like 'name:"ibm T63 notebook"' , it regard this as a PhrazeQuery,so it
will use PhrazeQuery.
but i want to get a result which include "ibm" and "T63" and "notebook" at
any postion. for example ,it should match some sentence like "i have a
notebook ,it is t63 of ibm"..
but solr doesn't do that,it consider that queryparser as a PhrazeQuery, how
can i do that as my mind?
2008/8/18, Shalin Shekhar Mangar <sh...@gmail.com>:
>
> Actually we have commit and optimize as separate request parameters
> defaulting to true for both full-import and delta-import. You can add a
> request parameter optimize=false for delta-import if you want to commit but
> not to optimize the index.
>
> I've updated the wiki. Thanks for pointing it out.
>
> On Mon, Aug 18, 2008 at 7:33 AM, Norberto Meijome <freebsd@meijome.net
> >wrote:
>
> > Hi again,
> >
> > I see in the DIH wiki page :
> > [...]
> > full-import [..]
> > commit: (default 'true'). Tells whether to commit+optimize after the
> > operation
> > [...]
> >
> > but nothing for delta-import... I think it would be useful , a 'commit'
> > (default=true) , 'optimize' (default=false) for the delta-import - these
> > should most probably be separate ones, i think.
> >
> > - for full-import , wouldn't it make sense to split commit + optimize
> into
> > 2 different options? Granted, if I do a clean=true, i'd probably want
> > (need!) an optimize... even then, optimize may be too slow / use too much
> > memory at that point in time... ? ( not too sure about this argument..)
> >
> > cheers,
> > B
> > _________________________
> > {Beto|Norberto|Numard} Meijome
> >
> > Never take Life too seriously, no one gets out alive anyway.
> >
> > I speak for myself, not my employer. Contents may be hot. Slippery when
> > wet. Reading disclaimers makes you go blind. Writing them is worse. You
> have
> > been Warned.
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
Re: DIH - commit / optimize
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
Actually we have commit and optimize as separate request parameters
defaulting to true for both full-import and delta-import. You can add a
request parameter optimize=false for delta-import if you want to commit but
not to optimize the index.
I've updated the wiki. Thanks for pointing it out.
On Mon, Aug 18, 2008 at 7:33 AM, Norberto Meijome <fr...@meijome.net>wrote:
> Hi again,
>
> I see in the DIH wiki page :
> [...]
> full-import [..]
> commit: (default 'true'). Tells whether to commit+optimize after the
> operation
> [...]
>
> but nothing for delta-import... I think it would be useful , a 'commit'
> (default=true) , 'optimize' (default=false) for the delta-import - these
> should most probably be separate ones, i think.
>
> - for full-import , wouldn't it make sense to split commit + optimize into
> 2 different options? Granted, if I do a clean=true, i'd probably want
> (need!) an optimize... even then, optimize may be too slow / use too much
> memory at that point in time... ? ( not too sure about this argument..)
>
> cheers,
> B
> _________________________
> {Beto|Norberto|Numard} Meijome
>
> Never take Life too seriously, no one gets out alive anyway.
>
> I speak for myself, not my employer. Contents may be hot. Slippery when
> wet. Reading disclaimers makes you go blind. Writing them is worse. You have
> been Warned.
>
--
Regards,
Shalin Shekhar Mangar.