8000 AQL Query result changed for COLLECT used on empty data/array · Issue #7749 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

AQL Query result changed for COLLECT used on empty data/array #7749

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
CBlinguland opened this issue Dec 12, 2018 · 4 comments
Closed

AQL Query result changed for COLLECT used on empty data/array #7749

CBlinguland opened this issue Dec 12, 2018 · 4 comments
Assignees
@jsteemann
Labels
1 Bug 2 Fixed Resolution 3 AQL Query language related
Milestone
3.4.1

Comments

@CBlinguland
Copy link
CBlinguland commented Dec 12, 2018 •
edited
Loading

My Environment

  • ArangoDB Version: 3.4.0
  • Storage Engine: RocksDB
  • Deployment Mode: Single Server
  • Infrastructure: own
  • Operating System: Windows 10 (same on Linux (Debian Stretch))
  • Used Package: Windows Installer Debian or Ubuntu .deb

Component, Query & Data

Affected feature:
AQL query result differs between 3.4.0 and 3.3.20 (and lower?)

AQL query (if applicable):

FOR v IN []
COLLECT collection=PARSE_IDENTIFIER(v._id) INTO grp=v
RETURN {collection: collection,grp: grp}

Steps to reproduce

  1. Use the AQL query
  2. get result on ArangoDB 3.3.20
  3. get result on ArangoDB 3.4
  4. compare both results: surprise!

Problem:

The result for the same query executed on different version of ArangoDB Server differs.

V 3.3.20 returns:

[]

V 3.4 returns:

[
  {
    "collection": "(non-representable type)",
    "grp": []
  }
]

Expected result:

ArangoDB V 3.4 should return an empty array too (like V 3.3.20 does).
The changed query result breaks the logic in my project.
@OmarAyo OmarAyo added 1 Analyzing 3 AQL Query language related labels Dec 12, 2018
@konsultaner
Copy link
Contributor

I experienced the same behavior in all my queries.

@jsteemann jsteemann self-assigned this Dec 17, 2018
jsteemann added a commit that referenced this issue Dec 18, 2018
@jsteemann
issue #7749
847de4c
jsteemann added a commit that referenced this issue Dec 18, 2018
@jsteemann
fixed issue #7749
4b91d5b
jsteemann added a commit that referenced this issue Dec 18, 2018
@jsteemann
issue #7749 (#7794)
93d624d
jsteemann added a commit that referenced this issue Dec 19, 2018
@jsteemann
fixed issue #7749 (#7797)
b5e844f
@jsteemann jsteemann added this to the 3.4.1 milestone Dec 19, 2018
@jsteemann
Copy link
Contributor

Fixed in 3.4.1.

@maxkernbach maxkernbach added the 2 Fixed Resolution label Dec 19, 2018
@maxkernbach
Copy link
Contributor

Hi @CBlinguland,

version 3.4.1, which includes a fix for this issue, has been released.

Could you please give it a try?

@CBlinguland
Copy link
Author

Hi @maxkernbach,

your fix in version 3.4.1 (windows and linux) solved the problem for me.
Thanks for fixing this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsteemann jsteemann

Labels
1 Bug 2 Fixed Resolution 3 AQL Query language related
Projects
None yet
Milestone
3.4.1
Development

No branches or pull requests
5 participants
@jsteemann @konsultaner @maxkernbach @OmarAyo @CBlinguland
0