Add 3.5 Release Notes

[mengweieric]

Description

3.5 Release Notes

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• New PPL command checklist all confirmed.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff or -s.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • New SQL functions: addtotals, addcoltotals, transpose, mvcombine; expanded spath capabilities

• Enhancements

  • Performance improvements and better error handling
  • Compatible with OpenSearch/OpenSearch Dashboards 3.5.0

• Bug Fixes

  • Multiple stability and reliability fixes

• Documentation

  • Complete release notes and docs for version 3.5.0

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

Adds a new release notes document for OpenSearch SQL v3.5.0 listing categorized changes: Features, Enhancements, Bug Fixes, Infrastructure, Documentation, and Maintenance with PR references.

Changes

Cohort / File(s)	Summary
Release Notes release-notes/opensearch-sql.release-notes-3.5.0.0.md	New release notes file for version 3.5.0 detailing features (e.g., addtotals, addcoltotals, transpose, mvcombine, spath enhancements), enhancements, bug fixes, infrastructure updates, documentation changes, and maintenance tasks; no executable code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

skip-changelog

Suggested reviewers

• kavithacm
• ps48
• penghuo
• derek-ho
• LantaoJin
• noCharger

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add 3.5 Release Notes' directly and clearly summarizes the main change: adding a new release notes document for version 3.5.0.
Description check	✅ Passed	The description provides a brief statement about adding 3.5 Release Notes, which is directly related to the changeset that adds the release notes file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@release-notes/opensearch-sql.release-notes-3.5.0.0.md`:
- Line 9: The release notes contain a malformed Markdown bullet marker "* *
Implement spath command with field resolution..." — replace the double asterisk
sequence with a single "*" to render correctly (i.e., change the line in the
release-notes content so it reads "* Implement spath command with field
resolution ([`#5028`](https://github.com/opensearch-project/sql/pull/5028))").
Ensure no extra whitespace or duplicate markers remain so the item renders as a
normal list entry.
- Line 36: The release notes contain a malformed bullet marker "* * Support
profile option for PPL - Part II Implement operator level metrics
([`#5044`](https://github.com/opensearch-project/sql/pull/5044))"; replace the
duplicate "* *" with a single "*" so the line reads "* Support profile option
for PPL - Part II Implement operator level metrics
([`#5044`](https://github.com/opensearch-project/sql/pull/5044))" to fix
rendering.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@release-notes/opensearch-sql.release-notes-3.5.0.0.md`:
- Line 6: Rewrite the first bullet to a clear, consistent feature statement:
change "* Feature tonumber : issue `#4514` tonumber function as part of roadmap
`#4287` ([`#4605`](...))" to a concise phrase like "Added tonumber function (issue
`#4514`; roadmap `#4287`) — see PR `#4605`" so it reads consistently with other
bullets; locate the line containing "tonumber" and update the wording to follow
the "Added/Changed/Fixed <feature> (<issue refs>; PR #...)" style.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Tighten the wording for clarity.

The first feature bullet is hard to parse. Consider a clearer phrasing and consistent style with the rest of the list.

✍️ Proposed edit

-* Feature tonumber : issue `#4514` tonumber function as part of roadmap `#4287` ([`#4605`](https://github.com/opensearch-project/sql/pull/4605))
+* Add `tonumber` function (roadmap `#4287`, issue `#4514`) ([`#4605`](https://github.com/opensearch-project/sql/pull/4605))

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	* Feature tonumber : issue #4514 tonumber function as part of roadmap #4287 ([#4605](https://github.com/opensearch-project/sql/pull/4605))
	* Add `tonumber` function (roadmap `#4287`, issue `#4514`) ([`#4605`](https://github.com/opensearch-project/sql/pull/4605))

🤖 Prompt for AI Agents

In `@release-notes/opensearch-sql.release-notes-3.5.0.0.md` at line 6, Rewrite the
first bullet to a clear, consistent feature statement: change "* Feature
tonumber : issue `#4514` tonumber function as part of roadmap `#4287`
([`#4605`](...))" to a concise phrase like "Added tonumber function (issue `#4514`;
roadmap `#4287`) — see PR `#4605`" so it reads consistently with other bullets;
locate the line containing "tonumber" and update the wording to follow the
"Added/Changed/Fixed <feature> (<issue refs>; PR #...)" style.