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

[DOCS] Added release highlights for 6.3 #31256

Merged
merged 4 commits into from
Jun 12, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 41 additions & 2 deletions docs/reference/release-notes/highlights-6.3.0.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,45 @@
<titleabbrev>6.3.0</titleabbrev>
++++

coming[6.3.0]
Here are the highlights of features that were added in Elasticsaerch 6.3.0.

See also <<release-notes-6.3.0,{es} 6.3.0 release notes>>.
Refer to the <<release-notes-6.3.0,{es} 6.3.0 release notes>> for the full list
of changes in this release.

NOTE: We want your feedback on the experiemental features in this release! Let
us know what you’d like to see next and any problems you encounter.

=== SQL
This experimental feature enables users who are familiar with SQL to
use SQL statements to query Elasticsearch indices. In addition to querying
through the SQL API, you can use the Translate API to see how SQL queries
are translated to native ELasticsearch queries.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small typo: "ELas..."


The included SQL CLI provides a simple way to submit SQL queries to Elasticsearch.
Similarly, the Elasticsearch JDBC driver enables you to connect your favorite
JDBC-compatible tool to Elasticsearch.

For more information, see <<xpack-sql, SQL Access>>.

=== Rollups
This experimental feature enables you to summarize and store historical data
so that is still available for analysis, but consumes significantly less
storage space. This is particularly useful when you're working with monitoring
and metrics data where it's not feasible to retain the raw data indefinitely.

When you ask Elasticsearch to store a rollup of data, it also stores the underlying
statistics. For example, if you roll up an average, the sum and count are also
stored so that the average can be recomputed at query time. This enables you to
query both rolled up data and “live” data simultaneously using the standard
query DSL.

For more information, see <<xpack-sql, SQL Access>>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this be a link to rollups instead of SQL?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup. Darned copy/paste. :-)


=== Java 10 Support
Java 9 was a short-term release that reached EOL in March 2018. 6.3.0 introduces
support for Java 10, which is scheduled to reach EOL in September 2018.

If you are not comfortable with the rapid release cycle of Java short term
versions (and EOL dates), you can continue to use Java 8. See the
https://www.elastic.co/support/matrix#matrix_jvm[support matrix]
for all of the JVM options for Elasticsearch.