We've been seeing similar (intermittent) errors for some time but as yet
have been unable to build a standalone piece of code that reliably
generates the error.
One workaround I have tried is to ensure all nodes and relationships in a
query have an explicit identifier, e.g. dummy1, dummy2 and so on. Though
it's hard to even prove whether or not this helps.
Incidentally, I have seen such UNNAMED errors in both 1.9 and 2.0.
Cheers
Nige
On 2 May 2014 09:21, "Yu Gene Loh" <yug...@gmail.com> wrote:
> Same results on community versions of 2.0.1 and 2.1.0-M01.
>
>
> On Thursday, May 1, 2014 8:39:12 PM UTC+8, Michael Hunger wrote:
>>
>> Can you please share the versions you are using?
>>
>>
>> Am 01.05.2014 um 11:03 schrieb Yu Gene Loh <yug...@gmail.com>:
>>
>> Some queries are returning intermittent InvalidSyntax (Unknown
>> identifier) errors, even though they work most of the time and return
>> correct results without any errors.
>>
>> Can anyone shed some light? Thanks!
>>
>>
>> gene.
>>
>>
>>
>> The query…
>> MATCH (d:Workgroup), (b:Activity),
>> (d)<-[:ACTIVITY_OF]-(b)<-[r:ASSET_INPUT_OF|ASSET_OUTPUT_OF]-(a:Asset)<-[:
>> ASSET_TYPE_OF]-(aa:AssetType)
>>
>> WHERE aa.name IN ['Document']
>>
>> OPTIONAL MATCH (:Activity)<-[subs:SUBSCRIBED_BY]-(a)
>>
>> OPTIONAL MATCH (a)-[sel:SELECTED_BY]->(:Person {username: 'testuser'})
>>
>> OPTIONAL MATCH (a)-[:BELONGS_TO]->(dd:Workgroup)
>>
>> RETURN ID(b), ID(a), a.name,
>>
>> CASE TYPE(r)
>>
>> WHEN 'ASSET_INPUT_OF' THEN 'Input'
>>
>> WHEN 'ASSET_OUTPUT_OF' THEN 'Output'
>>
>> END AS inputoutput,
>>
>> a.category, a.owner, a.location, aa.name, COUNT(subs), COUNT(sel), d.code
>> + ' ' + ID(b) + '/A' + ID(a) as asset_code, COLLECT(dd.code) + a.owner
>> AS owner ORDER BY ID(a);
>>
>>
>> sometimes returns the following error…
>>
>>
>> Unknown identifier `d`.
>>> Unknown identifier ` UNNAMED8428111205143288671`.
>>> Unknown identifier ` UNNAMED-1827321063839507775`.
>>> Unknown identifier ` INTERNAL_AGGREGATE478402e2-
>>> 0455-48f0-a95f-29c36c56a8d6`.
>>> Unknown identifier ` INTERNAL_AGGREGATE71e3c595-
>>> 93c6-4a57-a4b3-3a02b2143747`.
>>> Unknown identifier ` UNNAMED7958746158675052802`.
>>> Unknown identifier ` UNNAMED2430603467466026493`.
>>> Unknown identifier ` UNNAMED6198074590133770465`.
>>> Unknown identifier ` UNNAMED-2526645446754961735`.
>>> Unknown identifier ` UNNAMED-6102135876980975330`.
>>> Unknown identifier ` UNNAMED-8703169606424011663`.
>>> Unknown identifier ` INTERNAL_AGGREGATE69db5735-
>>> 293e-4bf1-adce-dd084c69c741`.
>>>
>>> Neo.ClientError.Statement.InvalidSyntax
>>
>>
>>
>>
>> --
>> 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+un...@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.
