Ah, it's a bug allright... only when using the BatchInserterIndex. The
problem goes away if you add provider:lucene to the configuration map,
like:
persons= indexProvider.nodeIndex(persons,
MapUtil.stringMap(type,exact,
provider, lucene));
It will be fixed in M03, where the
good stuff, thanks Mattias
On Tue, Oct 26, 2010 at 12:49 AM, Mattias Persson matt...@neotechnology.com
wrote:
Ah, it's a bug allright... only when using the BatchInserterIndex. The
problem goes away if you add provider:lucene to the configuration map,
like:
persons=
Hi,
I'm trying out the new Index Framework Batch Inserter using version 1.2.M02.
I getting a No index provider 'null' found error when calling
graphDb.index().forNodes(persons) in my test code below
Exception in thread main java.lang.IllegalArgumentException: No index
provider 'null' found
at
Paddy,
just tested it, and it seems it only occurs when running standalone,
see the other mail. Seems to be a bug, and I think it is linked to the
behavior seen in the Python bindings, too.
Cheers,
/peter neubauer
VP Product Management, Neo Technology
GTalk: neubauer.peter
Skype
4 matches
Mail list logo