Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-23 Thread George & Sherin
Since I was using some code to generate dynamic indexes I could not extract
the problematic piece easily from the unmanaged extension we have.

I tried to create a simple utility which tries to do the same as the other
code with and embedded db
But the problem is that it times out on index creation

Meanwhile I have this question?

Is there a transaction log viewer or something which can show me what were
the commands in a transaction?

org.neo4j.kernel.api.exceptions.TransactionFailureException: Database
constraints have changed (txId=3937) after this transaction (txId=3936)
started, which is not yet supported. Please retry your transaction to
ensure all constraints are executed
In the above case basically I want to see what was the contents of the
transaction 3937 .
Is there a way to do that ?

I will create a defect as well to see with the code but it does not
reproduce the  original problem but stuck at a different place.

George S


On Sat, Apr 14, 2018 at 6:09 PM, George & Sherin 
wrote:

> Sure will do that later today or tommorow
>
>
> On Sat, Apr 14, 2018 at 5:52 PM, 'Michael Hunger' via Neo4j <
> neo4j@googlegroups.com> wrote:
>
>> Would you mind creating a GitHub issue at github.com/neo4j/neo4j sharing
>> your commands and error message
>>
>> You didn't share the actual queries that create the ` :12356Person`.
>>
>> Michael
>>
>> On Fri, Apr 13, 2018 at 5:38 AM, George & Sherin 
>> wrote:
>>
>>> Already present Constraint create constraint on (n:Tenant) assert n.id is
>>> unique
>>>  each of this transaction contain
>>> Txn1
>>> create (n:Tenant {id:1234})
>>> create constraint on (n:1234Person) assert n. <http://n.id/>ssn is
>>> unique
>>> Txn2
>>> create (n:Tenant {id:12356})
>>> create constraint on (n:12356Person) assert n. <http://n.id/>ssn is
>>> unique
>>>
>>> Txn3
>>> create (n:Tenant {id:12345})
>>> create constraint on (n:12345Person) assert n. <http://n.id/>ssn is
>>> unique
>>>
>>> When I look at it the data in any of the transactions are not affected
>>> by the new constraints added in the transaction.
>>>
>>> On Thu, Apr 12, 2018 at 10:34 PM, Lexia Fantasy 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> https://neo4j.com/developer/kb/explanation-of-error-database
>>>> -constraints-have-changed-txid-84-after-this-transaction-txi
>>>> d-81-started/
>>>>
>>>> I ran into this problem
>>>> I have a constraint on label Tenant  id  is unique
>>>>
>>>> create constraint on (n:Tenant) assert n.id is unique
>>>>
>>>> Now when I create a  Tenant node with with label Tenant I am trying to
>>>> create a new unique constraint for another sets on nodes having labels
>>>> tenantidPersons
>>>> create constraint on (n:Persons) assert n.ssn is unique
>>>>
>>>> I am getting the below error when I try to multiple tenants
>>>> concurrently where each tenant creation try to create a constraint for its
>>>> persons
>>>>
>>>> org.neo4j.kernel.api.exceptions.TransactionFailureException: Database
>>>> constraints have changed (txId=3937) after this transaction (txId=3936)
>>>> started, which is not yet supported. Please retry your transaction to
>>>> ensure all constraints are executed
>>>>
>>>> As per the example the second constraint is only applicable for a
>>>> person is created in a tenant. But I get the error while creating the
>>>> tenant itself.
>>>>
>>>> Is this bug or expected behavior. IS the option only to retry the
>>>> transaction which does not sound right.
>>>>
>>>>
>>>> George S
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Neo4j" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to neo4j+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Neo4j" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to neo4j+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Neo4j" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to neo4j+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-14 Thread George &amp; Sherin
Sure will do that later today or tommorow


On Sat, Apr 14, 2018 at 5:52 PM, 'Michael Hunger' via Neo4j <
neo4j@googlegroups.com> wrote:

> Would you mind creating a GitHub issue at github.com/neo4j/neo4j sharing
> your commands and error message
>
> You didn't share the actual queries that create the ` :12356Person`.
>
> Michael
>
> On Fri, Apr 13, 2018 at 5:38 AM, George & Sherin 
> wrote:
>
>> Already present Constraint create constraint on (n:Tenant) assert n.id is
>> unique
>>  each of this transaction contain
>> Txn1
>> create (n:Tenant {id:1234})
>> create constraint on (n:1234Person) assert n. <http://n.id/>ssn is unique
>> Txn2
>> create (n:Tenant {id:12356})
>> create constraint on (n:12356Person) assert n. <http://n.id/>ssn is
>> unique
>>
>> Txn3
>> create (n:Tenant {id:12345})
>> create constraint on (n:12345Person) assert n. <http://n.id/>ssn is
>> unique
>>
>> When I look at it the data in any of the transactions are not affected by
>> the new constraints added in the transaction.
>>
>> On Thu, Apr 12, 2018 at 10:34 PM, Lexia Fantasy 
>> wrote:
>>
>>> Hi all,
>>>
>>> https://neo4j.com/developer/kb/explanation-of-error-database
>>> -constraints-have-changed-txid-84-after-this-transaction-
>>> txid-81-started/
>>>
>>> I ran into this problem
>>> I have a constraint on label Tenant  id  is unique
>>>
>>> create constraint on (n:Tenant) assert n.id is unique
>>>
>>> Now when I create a  Tenant node with with label Tenant I am trying to
>>> create a new unique constraint for another sets on nodes having labels
>>> tenantidPersons
>>> create constraint on (n:Persons) assert n.ssn is unique
>>>
>>> I am getting the below error when I try to multiple tenants concurrently
>>> where each tenant creation try to create a constraint for its persons
>>>
>>> org.neo4j.kernel.api.exceptions.TransactionFailureException: Database
>>> constraints have changed (txId=3937) after this transaction (txId=3936)
>>> started, which is not yet supported. Please retry your transaction to
>>> ensure all constraints are executed
>>>
>>> As per the example the second constraint is only applicable for a person
>>> is created in a tenant. But I get the error while creating the tenant
>>> itself.
>>>
>>> Is this bug or expected behavior. IS the option only to retry the
>>> transaction which does not sound right.
>>>
>>>
>>> George S
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Neo4j" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to neo4j+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Neo4j" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to neo4j+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to neo4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-12 Thread George &amp; Sherin
Already present Constraint create constraint on (n:Tenant) assert n.id is
unique
 each of this transaction contain
Txn1
create (n:Tenant {id:1234})
create constraint on (n:1234Person) assert n. ssn is unique
Txn2
create (n:Tenant {id:12356})
create constraint on (n:12356Person) assert n. ssn is unique

Txn3
create (n:Tenant {id:12345})
create constraint on (n:12345Person) assert n. ssn is unique

When I look at it the data in any of the transactions are not affected by
the new constraints added in the transaction.

On Thu, Apr 12, 2018 at 10:34 PM, Lexia Fantasy 
wrote:

> Hi all,
>
> https://neo4j.com/developer/kb/explanation-of-error-
> database-constraints-have-changed-txid-84-after-this-
> transaction-txid-81-started/
>
> I ran into this problem
> I have a constraint on label Tenant  id  is unique
>
> create constraint on (n:Tenant) assert n.id is unique
>
> Now when I create a  Tenant node with with label Tenant I am trying to
> create a new unique constraint for another sets on nodes having labels
> tenantidPersons
> create constraint on (n:Persons) assert n.ssn is unique
>
> I am getting the below error when I try to multiple tenants concurrently
> where each tenant creation try to create a constraint for its persons
>
> org.neo4j.kernel.api.exceptions.TransactionFailureException: Database
> constraints have changed (txId=3937) after this transaction (txId=3936)
> started, which is not yet supported. Please retry your transaction to
> ensure all constraints are executed
>
> As per the example the second constraint is only applicable for a person
> is created in a tenant. But I get the error while creating the tenant
> itself.
>
> Is this bug or expected behavior. IS the option only to retry the
> transaction which does not sound right.
>
>
> George S
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to neo4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Neo4j] Neo4j Data Migration from 2.x to 3

2018-04-03 Thread George &amp; Sherin
Hi Siddharta,

That was one other option but seems like a lot more expensive affair was
looking something cheaper like exclude indexes during the import.

George S

On Tue, Apr 3, 2018 at 11:56 AM, Siddhartha Sahu 
wrote:

> Hi George. How about exporting the data you want as csv files and
> importing them using the neo4j-import tool?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to neo4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Neo4j] Neo4j Data Migration from 2.x to 3

2018-04-03 Thread George &amp; Sherin
Thanks a lot Chris and Micheal.

I read that lucene indexes would be migrated. But I did not want to migrate
any of the indexes but instead rebuild all the indexes to use natives where
ever possible.

All I am looking for is just to migrate the Nodes,Relationships and Labels
and nothing else and for some time the system would run with no indexes
(too slow) but we add indexes on be one as the system is up.

Seems like there is no way to do that or my understanding is wrong.


George S



On Tue, Apr 3, 2018 at 7:46 AM, 'Chris Vest' via Neo4j <
neo4j@googlegroups.com> wrote:

> Existing indexes are kept in Lucene on upgrade. If you want to switch to
> the native schema index implementation, you opt-in on a per index basis by
> dropping and recreating the relevant schema indexes.
>
> --
> Chris Vest
> System Engineer, Neo Technology
>
>
> > On 3 Apr 2018, at 14.35, 'Michael Hunger' via Neo4j <
> neo4j@googlegroups.com> wrote:
> >
> > Hi George,
> >
> > The indexes are migrated automatically.
> >
> > If you already have schema indexes that will be taken care of.
> >
> > Michael
> >
> > On Fri, Mar 30, 2018 at 3:14 PM, Lexia Fantasy 
> wrote:
> > Hi all,
> >
> > I have a neo4j database which is currently running on 2.3.11. Now I am
> thinking of using the 3.x version. I am thinking of doing this
> >
> > Take an online back up of data from neo4j 2.x then
> > use import tool in 3.x to import the data and turn on db store migration
> on.
> >
> >
> > But my requirement is that since 3.x has native indexes. I would like to
> have only Nodes, Relationships and Labels in my 3.x instance and want to
> create the indexes and constraints I need after the migration
> >
> >
> > I did not see any option in the toolset which allows me to exclude
> indexes and constraints
> > Could some one throw some light on how I can achieve this, may be like
> deleting some directories in the backup data or so or some other alternate
> approach for this migration
> >
> > Regards
> > -George S
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Neo4j" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to neo4j+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Neo4j" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to neo4j+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to neo4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.