8000 Bug fix/internal issue #586 by Dronplane · Pull Request #9401 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

Bug fix/internal issue #586 #9401

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

Merged
merged 11 commits into from
Jul 4, 2019
Merged

Bug fix/internal issue #586 #9401

merged 11 commits into from
Jul 4, 2019

Conversation

Dronplane
Copy link
Contributor

Removed _analyzers collection lazy creation code.
Collection now always created so code was actually not used
Added minor fix to disable library loading for analyzer normalization calls.
Added logging of analyzer features in case of name collision detection

Fixed tests - added explicit creation for _analyzers collection as needed (due to removal of lazy creation).
Analyzer persistence checks in cluster moved from GTEST (as without actual DBServer mocked responces didn`t checked anything) to js tests (added checks for actual data stored in the _analyzers collection).

https://jenkins.arangodb.biz/job/arangodb-matrix-pr/5045/

@Dronplane Dronplane requested review from jsteemann and gnusi July 3, 2019 14:16
errorText << feature->name() << " ";
}
errorText << "'";
return arangodb::Result(TRI_ERROR_BAD_PARAMETER, errorText.str());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wouldn't this rather be an error with code TRI_ERROR_ARANGO_CONFLICT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description for this error says: "Will be raised when updating or deleting a document and a conflict has been detected."
But at this point we have no conflicts with documents, Most propbably this situation means that user actually have misspelled some of analyzer properties (e.g used the same name twice)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. For me "conflict" means "conflict", so I would have returned TRI_ERROR_ARANGO_CONFLICT. However, I can live with any other error code just fine.

@gnusi gnusi merged commit b70d737 into devel Jul 4, 2019
ObiWahn added a commit that referenced this pull request Jul 4, 2019
…ture/one-shard-db

* 'devel' of https://github.com/arangodb/arangodb:
  Bug fix/internal issue #586 (#9401)
  fix tests that didn't properly use env variable to look for test (#9399)
ObiWahn added a commit that referenced this pull request Jul 4, 2019
…ture/mimalloc

* 'devel' of https://github.com/arangodb/arangodb: (37 commits)
  improve handling when procdump detects the process is dead (#9381)
  Bug fix/internal issue #586 (#9401)
  fix tests that didn't properly use env variable to look for test (#9399)
  Pregel additional test & TSan error fix (#9357)
  use a lock when calling unload (#9375)
  @maierlars 😍 (#9394)
  fix typo (#9400)
  add initializeCursor back to DistinctCollectExecutor (#9386)
  Feature/add tcpdump support (#9396)
  apply filters before starting the server, so we can detect whether no test would be executed (#9387)
  [Devel] Queue-Full-Logging (#9388)
  add VelocyPackHelper::equal method (#9389)
  update velocypack version (#9379)
  Consistent formatting of CHANGELOG. (#9392)
  fix JSON statistics (#9385)
  undo removal (#9391)
  make sure all error code names are prefixed with ERROR_ @fceller @KVS85 (#9384)
  remove catch, refresh versions (#9390)
  fix invalid logId
  Fix ArangoSearch documentation examples
  ...
ObiWahn added a commit that referenced this pull request Jul 4, 2019
…-fix/oasis-statistics

* 'devel' of https://github.com/arangodb/arangodb:
  Don't use non-existent variable (#9407)
  relax test condition for windows (#9393)
  improve handling when procdump detects the process is dead (#9381)
  Bug fix/internal issue #586 (#9401)
  fix tests that didn't properly use env variable to look for test (#9399)
  Pregel additional test & TSan error fix (#9357)
  use a lock when calling unload (#9375)
  @maierlars 😍 (#9394)
  fix typo (#9400)
  add initializeCursor back to DistinctCollectExecutor (#9386)
  Feature/add tcpdump support (#9396)
@fceller fceller deleted the bug-fix/internal-issue-#586 branch July 30, 2019 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0