-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
477 history migration not working #496
Conversation
I'm benchmarking 3 approaches: based on Benchmarking parameters used were backend and index type, consisting of (in order) |
dab6494
to
b6dc12a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for cleaning up the benchmark namespaces a bit. In the future, please make things like that a separate PR though with an appropriate subject.
756605a
to
3ee4288
Compare
|
8d04e9e
to
b0abb7a
Compare
b0abb7a
to
1fb9f03
Compare
1fb9f03
to
d44f9c1
Compare
…orderly group-by results
…th custom configs as well as presets
…ring each benchmarking iteration into one point
…ng into multiple rounds
…upport. Tests to follow.
…nd my own carelessness)
…ith history, and retract otherwise
…hmarking measurements on separate database instances
d44f9c1
to
00323f7
Compare
SUMMARY
Include historical datoms in
datahike.migrate
export, so history is not lost in migration as would happen currently. #477Checks
Bugfix
fixes #number
CHANGELOG.md
updated