List Info

Thread: contrib additions in 2.0




contrib additions in 2.0
user name
2006-05-25 08:13:36
I'd like to commit the following two submissions...

http:
//issues.apache.org/jira/browse/LUCENE-496
http:
//issues.apache.org/jira/browse/LUCENE-577

...but it's not clear to me wether the best time to do that
is before or
after the 2.0 release:

* neither patch fixes a bug, which suggests i should hold
off since 2.0 is
ment to be a release containing primarily the removal of
deprecated
methods and big fixes since 1.9
	...but...
* neither makes any functionality change, they only add new
functionality
to contrib/miscellaneous making them extremely
"safe" from a change/risk
management perspective.


My gut says go ahead and commit them (ASAP if the plan is to
release 2.0
this weekend), but as the guy that submited both of them, i
feel like
maybe i'm not the most impartial person to decide.



Thoughts?



-Hoss


------------------------------------------------------------
---------
To unsubscribe, e-mail: java-dev-unsubscribelucene.apache.org
For additional commands, e-mail: java-dev-helplucene.apache.org

Breaking up text in fields or aggregate fields idea or field inheritance
user name
2006-05-25 09:00:04

Greetings,

I am struggling with the following.  Say I want to use
Lucene to search a
corporate phone book where I have workers from a database:

Workers
-------
John Douglas
Davis Raymond

My first thought was to create a field called workers and
put all the names
in it:

worker: john douglas davis raymond

This works ok except now a search for "douglas
davis" returns a hit, when no
such person exists. So to fix, create a workers field for
every person:

worker: john douglas
worker: davis raymond

Ok all set, because I can just prepend "worker:"
to any search.  But now say
I want to add a new category called 'manager':

Managers
--------
Mark Smith
Pearson Jones

I can do the same thing, but now I have two field types, and
the search
input is getting more complex.  All I want to do is have one
big field with
a separator where I need it:

content: john douglas \n davis raymond \n mark smith \n
pearson jones

But when I try this, the "\n" character is
treated as a space, so phrase
searches find people that do not exist.  Now I think I can
make a custom
filter to fix this, but is there an easy way to do this?  Is
there a
puncuation character that 'splits' text to avoid phrase
search hits?  Is
there an 'aggregate field' or 'field inheritance'
function, such as
content=<worker>+<manager>?

Thanks in advance,
JMA


------------------------------------------------------------
---------
To unsubscribe, e-mail: java-dev-unsubscribelucene.apache.org
For additional commands, e-mail: java-dev-helplucene.apache.org

contrib additions in 2.0
user name
2006-05-25 10:15:30
I think having these committed to the contrib area is ok
prior to  
2.0.   Let's see what others say.

	Erik

On May 25, 2006, at 4:13 AM, Chris Hostetter wrote:

>
> I'd like to commit the following two submissions...
>
> http:
//issues.apache.org/jira/browse/LUCENE-496
> http:
//issues.apache.org/jira/browse/LUCENE-577
>
> ...but it's not clear to me wether the best time to do
that is  
> before or
> after the 2.0 release:
>
> * neither patch fixes a bug, which suggests i should
hold off since  
> 2.0 is
> ment to be a release containing primarily the removal
of deprecated
> methods and big fixes since 1.9
> 	...but...
> * neither makes any functionality change, they only add
new  
> functionality
> to contrib/miscellaneous making them extremely
"safe" from a change/ 
> risk
> management perspective.
>
>
> My gut says go ahead and commit them (ASAP if the plan
is to  
> release 2.0
> this weekend), but as the guy that submited both of
them, i feel like
> maybe i'm not the most impartial person to decide.
>
>
>
> Thoughts?
>
>
>
> -Hoss
>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: java-dev-unsubscribelucene.apache.org
> For additional commands, e-mail: java-dev-helplucene.apache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: java-dev-unsubscribelucene.apache.org
For additional commands, e-mail: java-dev-helplucene.apache.org

contrib additions in 2.0
user name
2006-05-25 17:13:50
Chris Hostetter wrote:
> My gut says go ahead and commit them (ASAP if the plan
is to release 2.0
> this weekend), but as the guy that submited both of
them, i feel like
> maybe i'm not the most impartial person to decide.

+1

For new code that cannot break existing functionality the
bar is lower.

Doug


------------------------------------------------------------
---------
To unsubscribe, e-mail: java-dev-unsubscribelucene.apache.org
For additional commands, e-mail: java-dev-helplucene.apache.org

[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )