Correct ... it is the unfortunate side effect of having some legacy tables in uppercase :-\ I thought the explicit declaration of field name attribute was ok.

- Jon

On Nov 19, 2008, at 11:53 PM, Noble Paul നോബിള്‍ नोब्ळ् wrote:

So originally you had the field declaration as follows . right?
<field column="DOCID" template="PLAYER-${players.PLAYERID}"/>

we did some refactoring to minimize the object creation for
case-insensitive comparisons.

I guess it should be rectified soon.

Thanks for bringing it to our notice.
--Noble





On Thu, Nov 20, 2008 at 10:05 AM, Jon Baer <[EMAIL PROTECTED]> wrote:
Schema:
<field name="docid" type="string" indexed="true" stored="true"/>

DIH:
<field column="DOCID" name="docid" template="PLAYER-$ {players.PLAYERID}"/>

The column is uppercase ... isn't there some automagic happening now where
DIH will introspect the fields @ load time?

- Jon

On Nov 19, 2008, at 11:11 PM, Noble Paul നോബിള്‍ नोब्ळ् wrote:

Hi John,
it could probably not the expected behavior?

only 'explicit' fields must be case-sensitive.

Could you tell me the usecase or can you paste the data-config?

--Noble






On Thu, Nov 20, 2008 at 8:55 AM, Jon Baer <[EMAIL PROTECTED]> wrote:

Sorry I should have mentioned this is from using the DataImportHandler
...
it seems case insensitive ... ie my columns are UPPERCASE and schema
field
names are lowercase and it works fine in 1.3 but not in 1.4 ... it seems strict. Going to resolve all the field names to uppercase to see if that
resolves the problem.  Thanks.

- Jon

On Nov 19, 2008, at 6:44 PM, Ryan McKinley wrote:

schema fields should be case sensitive...  so DOCTYPE != doctype

is the behavior different for you in 1.3 with the same file/ schema?


On Nov 19, 2008, at 6:26 PM, Jon Baer wrote:

Hi,

I wanted to try the TermVectorComponent w/ current schema setup and I
did
a build off trunk but it's giving me something like ...

org.apache.solr.common.SolrException: ERROR:unknown field 'DOCTYPE'

Even though it is declared in schema.xml (lowercase), before I grep
replace the entire file would that be my issue?

Thanks.

- Jon






--
--Noble Paul





--
--Noble Paul

Reply via email to