[DRAFT] 30.0.0 release notes about druid HOT 7 OPEN

@frankgrimes97 Currently, Druid 30 is at a stage where only regressions can be backported.

from druid.

#16371 this PR added a feature to the Router page that makes it easier to search DataSource using keywords, which also changed user behavior, so it should be necessary to mention it in the release note I think 😄

from druid.

@asdf2014 That PR is not present in the Druid 30 branch, as it was merged after the branch cut (and cannot be backported as it is not a bugfix/regression).

from druid.

@adarshsanjeev Oh, I see 😅

from druid.

@adarshsanjeev Could the following in-progress bugfix #16550 be considered for 30.0.0? Not sure where you guys are in terms for release timeline/cadence but we'd ideally like to test/verify it on perhaps 30.0.0-rc3 instead of waiting for it to land in 31.0.0 in August/September.
We'd also be open to having it considered for a possible 29.0.2 release.
Thanks!

from druid.

Testing 30.0.0-rc3 there are a number of regressions im noticing in the UI,

1. Seems like the "supervisors" UI tab doesnt have a way to paginate all the supervisors anymore that was available in 29.0.1
2. Filtering in the "supervisors" UI tab by status = running return a UI exception "druidException/Column 'status' not found in any table (line[11], column[7])" - This issue is due to the client making a call to the druid/sql endpoint using a SELECT statement that does not have the STATUS column included. Thus it returns the above error. This is easy enough to fix and merely requires adding the column status to the SELECT query when fetching the status of the supervisors from the sys.supervisors table.

from druid.

@acherla Thanks for testing the RC.
These seem to be valid regressions, and should be fixed by #16571. Once it is backported, I will create a new RC3 build.

from druid.