Skip to content

DOC-2748-bug fixes added #852

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
wants to merge 3 commits into
base: 4.2.1-dev
Choose a base branch
from
+19 −0
Open

DOC-2748-bug fixes added #852

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4f1b5f1
DOC-2748-bug fixes added
Tushar-TG-14 Aug 4, 2025
f1414ed
DOC-2748-changes fixed
Tushar-TG-14 Aug 11, 2025
fcd584f
DOC-2748: Added 7 more bug fixes in 4.2.1 fixed issues
Tushar-TG-14 Aug 12, 2025
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
19 changes: 19 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 @@ -154,10 +154,29 @@ xref:4.2@tigergraph-server:data-loading:load-from-kafka-mm.adoc[] is still avail
==== Functionality

* Fixed missing error message when running a non-procedural GSQL query containing syntax errors at the end (GLE-10295).
* Eliminated false *REST-10015* error message when upserting a single vertex using the `gsql-atomic-level:atomic` flag via REST API (GLE-10680).
* Fixed a GPE crash caused by removing a cluster node or when a Disaster Recovery cluster has fewer replicas than the primary cluster (CORE-4967).
* Fixed the MaxFlow algorithm to return correct results, consistent with documented examples (GLE-10737).
* Fixed a UDF parsing error that failed to detect user-defined function names which conflict with built-in functions (GLE-10326).
* Fixed an issue where the system would throw a NullPointerException and fail to create or install a query during code validation (GLE-10501).
* Fixed an issue by skipping authentication when replaying requests in a Disaster Recovery cluster (GLE-10702).
* Fixed an issue that could cause upgrade failures by performing query and token bank compilation checks during the pre‑upgrade stage (GLE‑9459).

Copy link
Collaborator

Choose a reason for hiding this comment

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

  • Fixed an underflow error in the vertexCount function (CORE-5117).
  • Fixed a UDF parsing error which did not detect UDF names which conflict with built-in functions (GLE-10326).

==== Improvements

* Moved GSQL query and loading job compilation checks to the pre-check phase during upgrade to catch errors earlier and avoid manual fixes after upgrade (TP-7289).
* Reduced disk usage by removing on-disk indexes in cloud mode and deleting main files in both cloud and on-prem deployments (CORE-4930).
* Added support for extracting JWT certificates from JWKS by `kid` to handle automatic key rotation by identity providers (GLE-10001).
* Enhanced security for namespace-scoped TigerGraph Operator installations by separating the necessary cluster roles and namespace roles (TP-7024).
* Improved upgrade logs with a clearer message: *Installation of new TigerGraph version* (TP-8249).
* Added support for the `PRINT vt TO_CSV f` syntax to allow printing a vertex set directly to a CSV file (GLE-10523).

==== Security

* Eliminated a security vulnerability that allowed AWS credentials to be read in plain text using the `gadmin config get` command. These values are now masked (TP-8285).
* Fixed unauthorized exposure of graph name and creator information via the `/auth/simple` and `/internal/info` APIs (GLE-10746).
* Eliminated the potential exposure of personally identifiable information (PII) in loading job summary files by replacing detailed data with line numbers for invalid entries (TP-8575).
* Eliminated potential exposure of personally identifiable information (PII) in error messages when a loading job semantic check failed during creation (GLE-11125).


=== Fixed and Improved in 4.2.0
Expand Down