Received: by 10.236.173.201 with SMTP id v49mr12938443yhl.19.1349718560077;
        Mon, 08 Oct 2012 10:49:20 -0700 (PDT)
X-BeenThere: neo4j@googlegroups.com
Received: by 10.101.172.18 with SMTP id z18ls1336209ano.4.gmail; Mon, 08 Oct
 2012 10:49:18 -0700 (PDT)
Received: by 10.236.181.234 with SMTP id l70mr1806048yhm.5.1349718558383;
        Mon, 08 Oct 2012 10:49:18 -0700 (PDT)
Date: Mon, 8 Oct 2012 10:49:17 -0700 (PDT)
From: brian <blevine...@gmail.com>
To: neo4j@googlegroups.com
Message-Id: <778f6799-258f-448a-9749-1efb7d47cac0@googlegroups.com>
In-Reply-To: <D7F0ABA9-7089-4648-8D51-968F5F859615@neotechnology.com>
References: <7a15589e-5b7e-444f-93ab-dea18de8e1ba@googlegroups.com>
 <D7F0ABA9-7089-4648-8D51-968F5F859615@neotechnology.com>
Subject: Re: [Neo4j] mutating Cypher queries and auto-indexing
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_151_7896636.1349718557273"

------=_Part_151_7896636.1349718557273
Content-Type: multipart/alternative; 
	boundary="----=_Part_152_10987743.1349718557273"

------=_Part_152_10987743.1349718557273
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I'm not sure which of my questions you were answering "yes" to.  I probably 
should have phrased my question differently.  I think you're saying that 
nodes create/deleted using Cypher *should* be added/removed in the auto 
index?  Is that correct?

Thanks.

-brian

On Monday, October 8, 2012 1:07:25 PM UTC-4, Michael Hunger wrote:
>
> If you enabled and configured the auto-index to index the fields of such a 
> node, then yes. 
>
> Please note that index removal happens lazily when the nodes is requested 
> the next time from the index and not found in the graphdb. 
>
> Cheers 
>
> Michael 
>
> Am 08.10.2012 um 18:56 schrieb brian: 
>
> > Hello, 
> > 
> > I just wanted to confirm that my understanding is correct.  Is it true 
> that mutating Cypher queries do not affect auto-indexes?  For example, if I 
> create/delete a Node via a Cypher query, will the Node be added/removed 
> from the associated auto index? 
> > 
> > Thanks. 
> > 
> > -brian 
> > 
> > 
> > -- 
> >   
> >   
>
>
------=_Part_152_10987743.1349718557273
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

I'm not sure which of my questions you were answering "yes" to. &nbsp;I probably should have phrased my question differently. &nbsp;I think you're saying that nodes create/deleted using Cypher *should* be added/removed in the auto index? &nbsp;Is that correct?<div><br></div><div>Thanks.</div><div><br></div><div>-brian<br><div><br>On Monday, October 8, 2012 1:07:25 PM UTC-4, Michael Hunger wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">If you enabled and configured the auto-index to index the fields of such a node, then yes.
<br>
<br>Please note that index removal happens lazily when the nodes is requested the next time from the index and not found in the graphdb.
<br>
<br>Cheers
<br>
<br>Michael
<br>
<br>Am 08.10.2012 um 18:56 schrieb brian:
<br>
<br>&gt; Hello,
<br>&gt; 
<br>&gt; I just wanted to confirm that my understanding is correct. &nbsp;Is it true that mutating Cypher queries do not affect auto-indexes? &nbsp;For example, if I create/delete a Node via a Cypher query, will the Node be added/removed from the associated auto index?
<br>&gt; 
<br>&gt; Thanks.
<br>&gt; 
<br>&gt; -brian
<br>&gt; 
<br>&gt; 
<br>&gt; -- 
<br>&gt; &nbsp;
<br>&gt; &nbsp;
<br>
<br></blockquote></div></div>
------=_Part_152_10987743.1349718557273--

------=_Part_151_7896636.1349718557273--