Skip to content

(doc) Add doc for couple new feature flags introduced recently#3511

Merged
MonkeyCanCode merged 2 commits intoapache:mainfrom
MonkeyCanCode:new_feature_configruation_doc
Jan 23, 2026
Merged

(doc) Add doc for couple new feature flags introduced recently#3511
MonkeyCanCode merged 2 commits intoapache:mainfrom
MonkeyCanCode:new_feature_configruation_doc

Conversation

@MonkeyCanCode
Copy link
Contributor

Added doc for couple new feature flags.

Checklist

  • 🛡️ Don't disclose security issues! (contact [email protected])
  • 🔗 Clearly explained why the changes are needed, or linked related issues: Fixes #
  • 🧪 Added/updated tests with good coverage, or manually tested (and explained how)
  • 💡 Added comments for complex logic
  • 🧾 Updated CHANGELOG.md (if needed)
  • 📚 Updated documentation in site/content/in-dev/unreleased (if needed)

@github-project-automation github-project-automation bot moved this to PRs In Progress in Basic Kanban Board Jan 23, 2026
@MonkeyCanCode MonkeyCanCode changed the title (doc) Add doc for couple new feature flags (doc) Add doc for couple new feature flags introduced recently Jan 23, 2026
Copy link
Contributor

@evindj evindj left a comment

Choose a reason for hiding this comment

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

LGTM, I wonder if there is a way to have lint rule that will be triggered when a new config is added but not present in the doc.

flyrain
flyrain previously approved these changes Jan 23, 2026
Copy link
Contributor

@flyrain flyrain left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks @MonkeyCanCode !

@github-project-automation github-project-automation bot moved this from PRs In Progress to Ready to merge in Basic Kanban Board Jan 23, 2026
dimas-b
dimas-b previously approved these changes Jan 23, 2026
@MonkeyCanCode
Copy link
Contributor Author

LGTM, I wonder if there is a way to have lint rule that will be triggered when a new config is added but not present in the doc.

Don't have a good solution ATM as these are all from the code base and this file is not generated automatically.

@MonkeyCanCode MonkeyCanCode dismissed stale reviews from dimas-b and flyrain via 7f9c386 January 23, 2026 18:32
@MonkeyCanCode
Copy link
Contributor Author

@flyrain @dimas-b @evindj do you mind review again? two more new features went in as of this morning by @dimas-b and we agreed to handle doc update outside those PRs (thus adding them in the current PR).

@MonkeyCanCode MonkeyCanCode merged commit 3e9f931 into apache:main Jan 23, 2026
15 checks passed
@github-project-automation github-project-automation bot moved this from Ready to merge to Done in Basic Kanban Board Jan 23, 2026
evindj pushed a commit to evindj/polaris that referenced this pull request Jan 26, 2026
…e#3511)

* Add doc for couple new feature flags

* Add doc for couple new feature flags
snazy added a commit to snazy/polaris that referenced this pull request Feb 11, 2026
* (doc) Outdated changelog (apache#3503)

* deduplicate storage requests when loading views. (apache#3488)

* dedup metadata fetch by reusing ops

* Update Gradle to 9.3.0 (apache#3514)

* Site: add tool to mark versioned-docs as "do not index" (apache#3485)

Adds a shell script to add the front-matter tags `robots: noindex` (HTML META tag) and `exclude_search: true` (local site search) for versioned docs for a specific version.

The rudimentary script handles only markdown files, not asciidoc files, because there are currently only .md files in the versioned-docs.

* feat(metrics): Evolve PolarisMetricsReporter interface with timestamp parameter and comprehensive documentation (apache#3468)

Enhance the `PolarisMetricsReporter` SPI interface by adding a timestamp parameter to the `reportMetric()` method, enabling accurate time-series metrics reporting to external systems.

* Make python version configuration in Makefile (apache#3510)

* Update max supported python version (apache#3509)

* (doc) Add doc for couple new feature flags introduced recently (apache#3511)

* Add doc for couple new feature flags

* Add doc for couple new feature flags

* (nit) Site: Fading anchor (apache#3522)

* Fading anchor

* Fading anchor

* Update doc to use /Users/richardliu rather than quoted tilde (apache#3472)

* Remove KMS policies when KMS is not configured and improved default KMS permission for RO/RW (apache#3493)

* Update triggers in "Hugo Site" workflow (apache#3518)

The `site.yml` workflow is currently triggered in the following scenarios:
1. A push to the `main` branch, using the state of the site and the workflow as on `main`.
2. A push to a `release/*`branch, using the state of the site and the workflow as on that release branch.

Notice that workflows get the repo state (from the checkout actions) and the workflow state as its on that particular branch.
Put in other words: if we'd have a change to some old `release/1.0.x` branch, the web site would be updated as it is defined on that `release/1.0.x` branch, which is wrong and not the intended behavior.

This change updates the workflow triggers to only run for pushes to the `main` branch, plus PRs against the `main` branch and when called from another workflow.

This is part of apache#3516

* Let `site/bin/checkout-releases.sh` pull the latest state (apache#3517)

The script `site/bin/checkout-releases.sh` is a convenience to get the `versioned-docs` branch locally. It is missing a `git pull` to get the latest state of that branch though, which can be confusing.

* Last merged commit 1bf72bc

---------

Co-authored-by: Yong Zheng <[email protected]>
Co-authored-by: Innocent Djiofack <[email protected]>
Co-authored-by: Anand K Sankaran <[email protected]>
Co-authored-by: Richard Liu <[email protected]>
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.

4 participants