field name limitations?

[Karl Wettin <ka...@gmail.com>]

I'm considering using complete class xpaths as field names. These  
might end up beeing several hundred letters long and contain some  
wierd letters. Should I expect running in to problems?

Field names might look something like this:

the.absolute:Class.Path/@attribute/tokenizationStrategyA
the.absolute:Class.Path/@attribute/tokenizationStrategyB
the.absolute:Class.Path/someMethod()/tokenizationStrategy
the.absolute:Class.Path/denormalizedAssociation/@attribute/ 
tokenizationStrategy



-- 
karl

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org

Re: field name limitations?

[Yonik Seeley <yo...@apache.org>]

Should be fine.
The biggest issue may be the number of fields you are likely to have.
They are all kept in an in-memory map.  Also, during segment merging,
the field properties are merged in a linear fashion by stepping over
each one.

-Yonik

On 9/19/07, Karl Wettin <ka...@gmail.com> wrote:
> I'm considering using complete class xpaths as field names. These
> might end up beeing several hundred letters long and contain some
> wierd letters. Should I expect running in to problems?
>
> Field names might look something like this:
>
> the.absolute:Class.Path/@attribute/tokenizationStrategyA
> the.absolute:Class.Path/@attribute/tokenizationStrategyB
> the.absolute:Class.Path/someMethod()/tokenizationStrategy
> the.absolute:Class.Path/denormalizedAssociation/@attribute/
> tokenizationStrategy

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org