zachjsh 5e05858ff7 Catalog granularity accepts query format (#16680) ... Previously, the segment granularity for tables in the catalog had to be defined in period format, ie `'PT1H'` , `'P1D'`, etc. This disallows a user from defining segment granularity of `'ALL'` for a table in the catalog, which may be a valid use case. This change makes it so that a user may define the segment granularity of a table in the catalog, as any string that results in a valid granularity using either the `Granularity.fromString(str)` method, or `new PeriodGranularity(new Period(value), null, null)`, and that granularity maps to a standard supported granularity, where `GranularityType.isStandard(granularity)` returns true. As a result a user may who wants to assign a catalog table's segment granularity to be hourly, may assign the segment granularity property of the table to be either `PT1H`, or `HOUR`. These are the same formats accepted at query time.		2024-07-02 12:14:28 -04:00
..
java/org/apache/druid/testsEx	Catalog granularity accepts query format (#16680)	2024-07-02 12:14:28 -04:00
resources	Remove index_realtime and index_realtime_appenderator tasks (#16602)	2024-06-24 20:13:33 -07:00