We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From @Ziink on September 24, 2015 16:26
Enhancement request.
If we can label the fields making up the key in a manual lucene index, it will make the search capability more versatile.
See Issue 27
Copied from original issue: orientechnologies/orientdb-lucene#72
The text was updated successfully, but these errors were encountered:
Could you elaborate more your request? Maybe writing down a pseudo-SQL or Java statement and expected results. Thanks
Sorry, something went wrong.
Suggested use from @wouterv initial issue
create index index_name ('id','name') FULLTEXT ENGINE LUCENE STRING, STRING
Then be able to insert like
insert into index:index_name (id, name, rid) values (1, 'jeff', #45:0) insert into index:index_name (id, name, rid) values (1, 'Luca', #45:0) insert into index:index_name (id, name, rid) values (2, 'Luca', #45:1)
and then query stuff like
select * from index:index_name where [id, name] LUCENE "(id:1 OR name:Luca)"
robfrank
No branches or pull requests
From @Ziink on September 24, 2015 16:26
Enhancement request.
If we can label the fields making up the key in a manual lucene index, it will make the search capability more versatile.
See Issue 27
Copied from original issue: orientechnologies/orientdb-lucene#72
The text was updated successfully, but these errors were encountered: