-
Notifications
You must be signed in to change notification settings - Fork 993
[DOCS] Add missing items to 8.0.0-rc1 release notes #1863
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
jrodewig
merged 2 commits into
elastic:8.0
from
jrodewig:docs__add-missing-8.0.0-rc1-rns
Jan 12, 2022
+21
−0
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,6 +14,27 @@ https://github.com/elastic/elasticsearch-hadoop/pull/1808[#1808] | |
- Update Gradle wrapper to 7.3 | ||
https://github.com/elastic/elasticsearch-hadoop/pull/1809[#1809] | ||
|
||
- Update log4j version | ||
https://github.com/elastic/elasticsearch-hadoop/pull/1828[#1828] | ||
|
||
Serialization:: | ||
- Add support for the `date_nanos` field type | ||
https://github.com/elastic/elasticsearch-hadoop/pull/1803[#1803] | ||
|
||
Spark:: | ||
- Add support for Spark 3.1 and 3.2 | ||
https://github.com/elastic/elasticsearch-hadoop/pull/1807[#1807] | ||
|
||
[[bug-8.0.0-rc1]] | ||
[float] | ||
=== Bug fixes | ||
|
||
Spark:: | ||
- Resolve `saveToEs` saves case classes fields with `NULL` values | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These two in the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks. I moved them under |
||
https://github.com/elastic/elasticsearch-hadoop/pull/1478[#1478] | ||
|
||
- Correctly reading empty fields in as null rather than throwing exception | ||
https://github.com/elastic/elasticsearch-hadoop/pull/1816[#1816] | ||
|
||
- Setting es.read.fields.include could throw a NullPointerException in older spark version | ||
https://github.com/elastic/elasticsearch-hadoop/pull/1822[#1822] |
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.
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.
@masseyke @jbaiera This isn't in the list at #1859 (comment), but I think it should be included here.
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.
Sounds good to me. We don't actually ship log4j, so it's just a compile-time dependency. But probably worth mentioning even that since the log4j bug was such a high-profile thing.