Skip to content
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

The different way to handle UUID into __id and UUID into document #736

Open
akitoshka opened this issue Aug 30, 2017 · 1 comment
Open

Comments

@akitoshka
Copy link

akitoshka commented Aug 30, 2017

There are two different approachs how the mongo-connector handles UUID.
The first approach looks like into elastic2_doc_manager, doc-manager sets UUID into Elasticsearch as is, using default str method (with '-' delimiters)
The second approach looks like as into formatter, mongo-connector get hex value (without delimiters).
So we have different behaviors if we work with __id or UUID into doc.
It is unexpected behavior.

@akitoshka
Copy link
Author

akitoshka commented Aug 30, 2017

Pull request #737

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

No branches or pull requests

1 participant