Skip to content

DOC-3132: Added bug fixes for 4.2.3 #917

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.

Sign up for GitHub

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

Open
Tushar-TG-14 wants to merge 1 commit into
base: 4.2.3-dev
Choose a base branch
from
Open

DOC-3132: Added bug fixes for 4.2.3 #917

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions modules/release-notes/pages/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,19 @@ xref:4.2@tigergraph-server:data-loading:load-from-kafka-mm.adoc[] is still avail

== Fixed issues

=== Fixed and Improved in 4.2.3

==== Functionality

* Fixed an issue where binary files were still written during segment rebuild even after the segment was deleted, causing unnecessary disk usage (CORE-5356).
* Fixed an issue where gcollect could panic when encountering malformed NGINX log entries during log processing (TP-9128).
* Fixed an issue where repeated backups took progressively longer despite minimal data growth, caused by inefficient processing of schema changes (CORE-5360).
* Fixed an issue where partition configuration recovery could result in schema inconsistencies when config.yaml was missing but segment data existed (CORE-5376, CORE-5381).
* Fixed an issue that caused intermittent errors during legacy token validation (GLE-11715).
* Fixed an issue where token generation could become unresponsive during schema change operations by optimizing the workflow (GLE-11727).
* Fixed an issue where requests on port 14240 could not be routed directly to a specific RESTPP node when direct node-level access was required (TP-9198).
* Fixed an issue where password policies intended for native users were incorrectly enforced on LDAP proxy users (GLE-11850).

=== Fixed and Improved in 4.2.2

==== Functionality
Expand Down