DRAFT Setup documentation #215
Draft
Conversation
This file contains 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
in order to achieve support for multiple ES schemas - adds configuration for different schema locations - moves code from executables into Datura::Elasticsearch module - Datura::Options combines settings into schema path
had suffered from errors and from gem deprecation warnings
the validator ensures that all fields have either an exact mapping OR match a dynamic template, at least as far as our current simple dynamic templates go. This may need to be adjusted in the future if we start using more complex templates refactors file_type post_es method to use Elasticsearch::Index object and to rely less on repeated "returns" vs a final line at the end also adds some helpful methods like should_post? to complement should_transform? for ease
that is, previously it was assuming that nested subfields all match a top level field or dynamic mapping actually, nested fields can specify their own specific mapping that the subfields may also access....sooooooo I had to redo stuff tests should be passing! thank goodness for unit tests and tdd
reverts my earlier change, it breaks other functions
update documentation for changes to the schema
in order to achieve support for multiple ES schemas - adds configuration for different schema locations - moves code from executables into Datura::Elasticsearch module - Datura::Options combines settings into schema path
the validator ensures that all fields have either an exact mapping OR match a dynamic template, at least as far as our current simple dynamic templates go. This may need to be adjusted in the future if we start using more complex templates refactors file_type post_es method to use Elasticsearch::Index object and to rely less on repeated "returns" vs a final line at the end also adds some helpful methods like should_post? to complement should_transform? for ease
This reverts commit b71d028.
wkdewey
force-pushed
the
setup_documentation
branch
from
3f78ce0
to
4c65fb0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
adding some new documentation for starting a new repo