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

IGNITE-20926 Added 2.16 release notes. #11070

Merged
merged 9 commits into from
Nov 29, 2023

Conversation

NSAmelchev
Copy link
Contributor

Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

If you need any help, please email [email protected] or ask anу advice on http://asf.slack.com #ignite channel.

(!) WARNINGS:
* Operations on atomic caches within transactions are finally forbidden. The system property IGNITE_ALLOW_ATOMIC_OPS_IN_TX has been removed.
* Removed CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT cache mode.
* Mixed atomicity cache groups now restricted, but IGNITE_ALLOW_MIXED_CACHE_GROUPS system option may temporarily allow them.
Copy link
Contributor

Choose a reason for hiding this comment

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

"Mixed atimicity and transactional" or something like "Mixed mode",
"restricted" - > "forbidden"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

Ignite:
* Added ARM64 Docker images.
* Added CLIENT_CONNECTION_ATTRIBUTES system view.
* Added IndexQuery to performance statistics.
Copy link
Contributor

Choose a reason for hiding this comment

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

Perhaps swap the words: "performance statistics for IndexQuery"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

* Fixed list of reserved keywords.
* Fixed memory leak in MailboxRegistryImpl#remotes.
* Fixed performance statistics gathering.
* Fixed placeholder values from ModifyNode (backport of IGNITE-19096).
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove "backport of IGNITE-19096", it's a ticket from Ignite-3

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

Comment on lines 17 to 18
* Added JMX commands invoker.
* Added a description check if the command argument is enum type.
Copy link
Contributor

Choose a reason for hiding this comment

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

It's hard to understand for end user what these lines are about.
Perhaps group all management API related tickets to somethink like "Added management API (common interface to ...)"?

* Added client session outbound message queue size limit.
* Added compact footer usage statistics to the idle_verify command.
* Added descriptions and values to the properties list command.
* Added documentation for the Index Reader Utility.
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we really need documentation tickets in release notes? Documentation even not in release package.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

* Added number of partitions processed by the index worker to the output of the index commands.
* Added performance statistics info about query properties and processed rows count by query.
* Added support of SslContextFactory to CommandHandler (instead of GridSslBasicContextFactory).
* Added support of cache group filter for dumps.
Copy link
Contributor

Choose a reason for hiding this comment

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

We have "Added cache dumps" in this release, perhaps we don't need another tickets in release notes related to dumps

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

* Added performance statistics info about query properties and processed rows count by query.
* Added support of SslContextFactory to CommandHandler (instead of GridSslBasicContextFactory).
* Added support of cache group filter for dumps.
* Added support of custom SSL factory to the control.sh utility.
* Added support of custom location for cache dumps.
Copy link
Contributor

Choose a reason for hiding this comment

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

This line related to dumps too.

(!) WARNINGS:
* Operations on atomic caches within transactions are finally forbidden. The system property IGNITE_ALLOW_ATOMIC_OPS_IN_TX has been removed.
* Removed CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT cache mode.
* Mixed mode cache groups now restricted, but IGNITE_ALLOW_MIXED_CACHE_GROUPS system option may temporarily allow them.

Choose a reason for hiding this comment

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

Suggestion: are now restricted

* Operations on atomic caches within transactions are finally forbidden. The system property IGNITE_ALLOW_ATOMIC_OPS_IN_TX has been removed.
* Removed CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT cache mode.
* Mixed mode cache groups now restricted, but IGNITE_ALLOW_MIXED_CACHE_GROUPS system option may temporarily allow them.
* The ignite-ml, cassandra modules have been migrated to the Ignite extensions.

Choose a reason for hiding this comment

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

Suggestion: The ignite-ml and cassandra modules

* Added JMX commands invoker.
* Added ability to configure metric exporter filter from Spring XML.
* Added cache dumps.
* Added client session outbound message queue size limit.

Choose a reason for hiding this comment

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

Suggestion: Added size limit of the client session outbound message queue.

* Fixed StoredCacheData removing when a node filter is set.
* Fixed WAL logging to an archived segment after node restart.
* Fixed an issue when IgniteLock cannot be acquired after release on JDK 17.
* Fixed an issue when TTL isn't set for entries inserted with "insert from select" query.

Choose a reason for hiding this comment

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

Suggestion: is not set

* Fixed WAL logging to an archived segment after node restart.
* Fixed an issue when IgniteLock cannot be acquired after release on JDK 17.
* Fixed an issue when TTL isn't set for entries inserted with "insert from select" query.
* Fixed an issue when a transaction will never become finished on timeout when deadlock detection is disabled.

Choose a reason for hiding this comment

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

Suggestion: Fixed an issue when a transaction never finishes on timeout when deadlock detection is disabled.

* Fixed an issue when IgniteLock cannot be acquired after release on JDK 17.
* Fixed an issue when TTL isn't set for entries inserted with "insert from select" query.
* Fixed an issue when a transaction will never become finished on timeout when deadlock detection is disabled.
* Fixed an issue where continuous queries could produce excessive memory usage.

Choose a reason for hiding this comment

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

Suggestion: Fixed an issue where continuous queries caused excessive memory usage.

* Fixed assertion error on defragmentation.
* Fixed broken serialization of communication messages due to incorrect GridCacheQueryRequest class marshalling.
* Fixed cache objects transformation in Java thin client.
* Fixed cache scan command page size to meet the limit argument.
Copy link

@Sashalig Sashalig Nov 28, 2023

Choose a reason for hiding this comment

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

Suggestion: Fixed the size of cache scan command page to meet the limit argument.

* Fixed cache scan command page size to meet the limit argument.
* Fixed connectable nodes list for control.sh.
* Fixed continuous queries backup ack message sending for expired entries.
* Fixed control-utility module location for slim and LGPL assemblies.

Choose a reason for hiding this comment

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

Suggestion: control utility

* Fixed connectable nodes list for control.sh.
* Fixed continuous queries backup ack message sending for expired entries.
* Fixed control-utility module location for slim and LGPL assemblies.
* Fixed defragmentation can't be configured to use one thread.
Copy link

@Sashalig Sashalig Nov 28, 2023

Choose a reason for hiding this comment

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

Suggestion: Fixed the Defragmentation can't be configured to use one thread issue.

* Fixed log message about sending and receiving partition file during snapshot restore.
* Fixed log message of snapshot create operation with the warning result.
* Fixed negative duration in the SQL query system view.
* Fixed node crash due to SecurityContext not being found during discovery message processing.

Choose a reason for hiding this comment

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

Suggestion: SecurityContext not found during...

* Fixed failure on planning when cache size exceeds Integer.MAX_VALUE.
* Fixed list of reserved keywords.
* Fixed memory leak in MailboxRegistryImpl#remotes.
* Fixed performance statistics gathering.

Choose a reason for hiding this comment

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

Suggestion: performance statistics collection

* Fixed performance statistics gathering.
* Fixed placeholder values from ModifyNode.
* Fixed primary key inline size calculation.
* Fixed query freezes when partitions are set.

Choose a reason for hiding this comment

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

Suggestion: Fixed the Query freezes when partitions are set issue.

@NSAmelchev NSAmelchev merged commit 2dc1951 into apache:master Nov 29, 2023
6 of 7 checks passed
NSAmelchev added a commit that referenced this pull request Nov 29, 2023
@NSAmelchev
Copy link
Contributor Author

@Sashalig, @alex-plekhanov, Thank you for the review!

Nastya828 pushed a commit to Nastya828/ignite that referenced this pull request Dec 11, 2023
simon-greatrix pushed a commit to simon-greatrix/ignite that referenced this pull request Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants