10000 Import via Web UI silently fails when new records violate an index constraint · Issue #10470 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

Import via Web UI silently fails when new records violate an index constraint #10470

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.

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

Closed
lacikawiz opened this issue Nov 19, 2019 · 2 comments
Closed
Assignees
Labels
1 Bug 2 Fixed Resolution 3 ImportExport Export / Import / Dump / Restore / Backup 3 UI ArangoDB Web Interface (frontend/Aardvark)
Milestone

Comments

@lacikawiz
Copy link

My Environment

  • ArangoDB Version: 3.5.0
  • Storage Engine: RocksDB
  • Deployment Mode: Single Server
  • Deployment Strategy: Manual Start
  • Configuration: Simple basic setup with defaults
  • Infrastructure: Own server
  • Operating System: Ubuntu 18.04
  • Total RAM in your machine: 8Gb.
  • Disks in use: SSHD
  • Used Package: Built from source (no changes)

Component, Query & Data

Affected feature:
Import data into collection via web interface (aardvark)

AQL query (if applicable):

AQL explain (if applicable):

Dataset:
Simple records like this:

{
  "Name": {
    "ru": "Фильтр масляный двигателя",
    "en": "Engine oil filter"
  },
  "src": {
    "existru": {
      "lastcheck": 0,
      "id": "7"
    }
  }
}

Size of your Dataset on disk:
n/a

Replication Factor & Number of Shards (Cluster only):
n/a

Steps to reproduce

  1. Log in to the Web UI (eg: localhost::8529 ), select your database, and create an empty document collection.
  2. Set up a hash index on a collection with the "unique" option set
  3. Import a JSON file into the collection which is either missing the values for the index, or have duplicate values

Problem:
The documents which violate the constraint are not getting imported. Eg, if the key of the index is missing then only one record will be imported, all others won't.
The UI gives no error message, or any kind of indication as to why the documents are not imported. Not even checking the network traffic reveals any information.

Expected result:
Provide an error message, something to the effect "document x was not imported due to unique constraint violation - in index xyz"

@OmarAyo
Copy link
Contributor
OmarAyo commented Nov 20, 2019

Hi @lacikawiz

Thanks for reporting this, we reproduce this internally and we will fwd your request internally

By the way, if you try to execute the import operation from arangoimp you will get a proper error message - something like:

2019-11-20T11:47:36Z [14825] WARNING [e5a29] at position 0: creating document failed with error 'unique constraint violated', offending document: {"_key":"356","_id":"test/356","_rev":"_ZmgcgBC--_","Nam1":"Omar"}

Best

@OmarAyo OmarAyo added 1 Bug 3 UI ArangoDB Web Interface (frontend/Aardvark) 3 ImportExport Export / Import / Dump / Restore / Backup labels Nov 20, 2019
@hkernbach hkernbach self-assigned this Nov 20, 2019
hkernbach added a commit that referenced this issue Nov 20, 2019
@hkernbach hkernbach mentioned this issue Nov 20, 2019
3 tasks
mchacki pushed a commit that referenced this issue Nov 21, 2019
* fixing issue #10470

* changelog

* changelog
hkernbach added a commit that referenced this issue Nov 21, 2019
hkernbach added a commit that referenced this issue Nov 21, 2019
ObiWahn added a commit that referenced this issue Nov 21, 2019
…ture/dump-db-properties

* 'devel' of https://github.com/arangodb/arangodb:
  Splicing gather cleanup (#10479)
  Feature/changelog for subquery splicing (#10396)
  Fix potential segfault (#9308)
  don't smile away exception
  fixing issue #10470 (#10491)
  add generated front end files in order to allow collection creation
  Added precondition to ensure that server is still as seen before. (#10468)
  Actually use the given format to execute a query (#10484)
  Fix SubqueryStartExecutor (#10488)
  add tests for inventory (#10464)
  fix truncate operation in synchronous replication (#10492)
KVS85 pushed a commit that referenced this issue Nov 22, 2019
* fixing issue #10470

* changelog

* Update CHANGELOG

* Rebuild UI

* updated grunt-contrib-imagemin

* add package-lock.json
KVS85 pushed a commit that referenced this issue Nov 22, 2019
* fixing issue #10470

* changelog

* Update CHANGELOG

* Rebuild UI

* updated grunt-contrib-imagemin

* add package-lock.json
KVS85 pushed a commit that referenced this issue Nov 27, 2019
* fixing issue #10470

* changelog
@maxkernbach maxkernbach added the 2 Fixed Resolution label Dec 10, 2019
@maxkernbach maxkernbach added this to the 3.5.3 milestone Dec 10, 2019
@maxkernbach
Copy link
Contributor

Hi @lacikawiz,

Version 3.5.3, which includes a fix for this issue, has been released.

From the Changelog:

Please find the latest release in the download section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 Bug 2 Fixed Resolution 3 ImportExport Export / Import / Dump / Restore / Backup 3 UI ArangoDB Web Interface (frontend/Aardvark)
Projects
None yet
Development

No branches or pull requests

4 participants
0