#12 docu 3.1.4 example quirk

[gennff]

hi,

working through the examples of docu 3.1.4 i experienced the following strange log output:

1.
iff i create the index without an extra column name for F2 like:
create index it1 on t1(f1) indextype is lucene.LuceneIndex parameters('ExtraCols:F2;FormatCols:F1(000),F2(/emp/name)');
i get in the log:
FINE: Document<stored,indexed<rowid:AAAWqqAAGAAABodAAA> indexed,tokenized<F1:001> indexed,tokenized<F2:ravi >>
FINE: Document<stored,indexed<rowid:AAAWqqAAGAAABodAAB> indexed,tokenized<F1:003> indexed,tokenized<F2:murthy >>

2.
iff i create the index with an extra column name for F2 like:
create index it1 on t1(f1) indextype is lucene.LuceneIndex parameters('ExtraCols:F2 "f2";FormatCols:F1(000),F2(/emp/name)');
i get in the log:
FINE: Document<stored,indexed<rowid:AAAWqqAAGAAABodAAA> indexed,tokenized<F1:001> indexed,tokenized<f2:1 ravi >>
FINE: Document<stored,indexed<rowid:AAAWqqAAGAAABodAAB> indexed,tokenized<F1:003> indexed,tokenized<f2:3 murthy >>

it seems that the f2 field gets populated with all of the text nodes of the xml iff some extra column name is used.

p

[gennff]

just to add: the log output also features an upper and a lower case field name as well as the query field identifier must also be upper or lower, depending on the case used in the create index.
p