feat: runtime parity for handling both ElasticSearch 6 and 7 upstreams#51
Merged
siddharthlatest merged 148 commits intodevfrom Dec 10, 2019
Merged
feat: runtime parity for handling both ElasticSearch 6 and 7 upstreams#51siddharthlatest merged 148 commits intodevfrom
siddharthlatest merged 148 commits intodevfrom
Conversation
feat: add billing
fix: size issue in Request Logs
fix: remove subscription_id
…ling * 'test/billing' of github.com:appbaseio/arc: fix: remove fmt.Println(..) log
…c into feat/runtime_es6_es7_parity
bietkul
commented
Dec 4, 2019
bietkul
changed the title
siddharthlatest
changed the title
Author
|
@siddharthlatest Fixed it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this do / why do we need it?
This PR merges the Arc codebase (which was previously separate) for ElasticSearch v6 and ElasticSearch v7.
What should your reviewer look out for in this PR?
Everything - it's a major refactor.
Do you need help or clarification on anything?
Which issue(s) does this PR fix?