Thanks Michael removing the graph.db/index/lucene.log.* helped and I am
able to access few of APIs. So I think we are good with upgrade.
Some complains for older version of cypher that uses ?.
and you _might_ need to create a transaction against an index, like
creating
an index and deleting it
If it already works fine, then all is good.
Michael
Am 18.06.2014 um 13:10 schrieb Mamta Thakur ghazal.ma...@gmail.com:
Thanks Michael removing the graph.db/index/lucene.log.* helped and I am able
to access few of APIs. So I think we are good with upgrade.
Some complains for older version
Hi,
I have been trying to upgrade neo4j from 1.9.3 to 2.0.3. SDN
from 2.3.1.RELEASE to 3.1.0.RELEASE.
Followed the steps listed
@
http://docs.neo4j.org/chunked/stable/deployment-upgrading.html#explicit-upgrade
I try bringing up the server with the upgrade configuration.There are a few
new
Btw. just got the info that it is fixed and will be part of 2.0.4
https://github.com/neo4j/neo4j/commit/37371aa (Thanks Jake!)
Michael
Am 17.06.2014 um 14:55 schrieb Michael Hunger
michael.hun...@neotechnology.com:
This is a know issue which is currently worked on,
can you delete the
Hi Michael,
Does that mean I will loose the existing index as well? How would any of my
queries work?
I fixed some of the @RelationshipEntity that did not have an @GraphId
required with 2.0.3.
Now I don't get this error on start up rather I get this error when
shutting down the server.
No, as you have a clean shutdown all the data is in the store.
Sent from mobile device
Am 17.06.2014 um 16:55 schrieb Mamta Thakur ghazal.ma...@gmail.com:
Hi Michael,
Does that mean I will loose the existing index as well? How would any of my
queries work?
I fixed some of the
