manual index bug

[publicocean0]

OrientDB Version, operating system, or hardware.

• v2.0 SNAPSHOT[ ] - .18[ ] .17[ ] .16[ ] .15[ ] .14[ ] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
• v2.1 SNAPSHOT[ ] - .16[ ] .15[ ] .14[ ] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
• v2.2 SNAPSHOT[ x ] - .rc1[ ] .beta2[ ] .beta1[ ]

Operating System

• [x ] Linux

• MacOSX

• Windows

• Other Unix

• Other, name?

  INSERT INTO INDEX:Manual (key, rid) VALUES(['Enrico', 'Rome'], Export of database [moved] #5:0)

orientdb> SELECT FROM INDEX:Manual WHERE key LUCENE "Enrico"

if want search for prop 1 and not for prop2 how to do?

select from index:Manual34 where [prop1, prop2] LUCENE "(prop1:foo AND prop2:bar)"

Error: com.orientechnologies.orient.core.exception.OCommandExecutionException: 'Key' field is required for queries against indexes

it seams there is no way for finding a specific property of schema

[wolf4ood]

did you try?
select from index:Manual34 where key LUCENE "(prop1:foo AND prop2:bar)"

[wolf4ood]

@publicocean0

sorry was't documented on multiple fields in manual index. Since it's manual and there aren't properties the engine generates the name k1,k2,k3..kN

select from index:Manual34 where key LUCENE "(k0:foo AND k1:bar)"

See
LuceneManualIndex test

[wolf4ood]

@publicocean0 the exception that you get is at parsing time because the key is mandatory in index: syntax

[publicocean0]

CREATE INDEX Manual11 FULLTEXT ENGINE LUCENE long , long ,long ,long
insert into index:Manual11 (key, rid) values([1,2,3,4],#30:3)

Inserted record '{rid:#30:3,key:[4]}' in 0,455000 sec(s).
select from index:Manual11 where key LUCENE "(k0:1)"

Error: com.orientechnologies.orient.core.exception.OCommandExecutionException: Error on execution of command: sql.select from index:Manual11 where key LUCENE "(k0:1)"

Error: java.lang.NumberFormatException: For input string: "(k0:1)"

[publicocean0]

CREATE INDEX Manual13 FULLTEXT ENGINE LUCENE string , string , string , string

Creating index...
Created index successfully with 0 entries in 0,337000 sec(s).

Index created successfully
insert into index:Manual13 (key, rid) values(['a','b','c','d'],#30:3)

Inserted record '{rid:#30:3,key:[4]}' in 0,327000 sec(s).

select from index:Manual13 where key LUCENE "k0:'a'"

0 item(s) found. Query executed in 0.227 sec(s).

OCompositeKey consider string entirely

[wolf4ood]

@publicocean0

the first one is a type problem. With lucene we support strings or list of strings

the second one you are not taking in account the Analyzer.

a is a stop word that is removed in indexing phase.

insert into index:Manual13 (key, rid) values(['Test','b','c','d'],#30:3)

select from index:Manual13 where key LUCENE "(k0:Test)"

[wolf4ood]

@publicocean0
is it working ?

[publicocean0]

select from index:Manual13 where key LUCENE "k0:Test"

Error: java.lang.NoClassDefFoundError: com/orientechnologies/orient/core/serialization/OBase64Utils

Error: java.lang.ClassNotFoundException: com.orientechnologies.orient.core.serialization.OBase64Utils

[publicocean0]

reading in the log
Error: java.lang.NumberFormatException: For input string: "(k0:1)"

so it is trying to parsing as number "(k0:1)"

[wolf4ood]

@publicocean0

tested without problem in 2.2.5 plocal and remote with the index created

in this way

CREATE INDEX Manual13 FULLTEXT ENGINE LUCENE string , string , string , string

[publicocean0]

i have 2.2.6.

i will try to recompile....

[wolf4ood]

Btw you get this

`Error: java.lang.NumberFormatException: For input string: "(k0:1)"```

from the query engine. This is an integration problem.
Because the fields are long and the param is a string.

[publicocean0]

same error after recompilation boh

select from index:Manual13 where key LUCENE "k0:Test"

Error: java.lang.NoClassDefFoundError: com/orientechnologies/orient/core/serialization/OBase64Utils

Error: java.lang.ClassNotFoundException: com.orientechnologies.orient.core.serialization.OBase64Utils

[publicocean0]

ok now it works in 2.6 ... a problem with console. restarting console it works.

It remains the problems with key for data type not string.

[wolf4ood]

@publicocean0
that is the sql engine check with types. Let me check if can do something about it

[publicocean0]

ok it is not urgent , i passed to another task in the while, fortunately i have a pile of tasks to do :)
In the while if you have a idea how to make a index for chunks (startoffset,endoffset,index) from a remote client saving the chunks inside a transaction (seekable file to read) i will go to london to make compliments to you :).

[publicocean0]

A similar problem is also in automatic lucene. I have a property long but when i make query no field is found

[wolf4ood]

hi @publicocean0

i guess, the code is the same.
We did integrate and test the text indexing of lucene.
The number handling was left out. We should extend the query parser of lucene in order to support numeric ranges.

[wolf4ood]

@publicocean0
For numbers you should use native indexing.

[publicocean0]

Impossible , my query in index needs to create a expression with indexed fields. It is a tipical case in which need lucene. In addition in future i need to search inside properties (embedded map defined by user on the fly). Unfortunatelly, indexes used as projections on single fixed fields are just a sub case of all possible ones.