Ah yes, milestone is fine. Thanks ! All good.
Regards JB On Thu, Apr 4, 2024 at 5:12 PM Eduard Tudenhoefner <edu...@tabular.io> wrote: > > There is the V3 Spec milestone where it's tracked (amongst other things). > > On Thu, Apr 4, 2024 at 9:44 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: >> >> Hi Eduard, >> >> Thanks for the update ! It makes sense to me. >> >> Maybe a GH label with spec or v3_spec would help to see what is planned for >> v3 ? >> >> Regards >> JB >> >> On Thu, Apr 4, 2024 at 9:36 AM Eduard Tudenhoefner <edu...@tabular.io> wrote: >> > >> > Type promotion from Long to Timestamp is on the roadmap for the V3 Spec, >> > so that would be the preferred way. >> > >> > On Wed, Apr 3, 2024 at 10:38 AM Jean-Baptiste Onofré <j...@nanthrax.net> >> > wrote: >> >> >> >> Hi Manu >> >> >> >> TIMESTAMP_LONG type promotion could be the easiest way, it would work >> >> with the existing transform. >> >> >> >> Would it work for you? >> >> >> >> Regards >> >> JB >> >> >> >> On Wed, Apr 3, 2024 at 5:56 AM Manu Zhang <owenzhang1...@gmail.com> wrote: >> >> > >> >> > Hi all, >> >> > >> >> > We have source data with a timestamp field in LONG type to land in an >> >> > Iceberg table. We want to partition the table with the timestamp field >> >> > such that we can query recent data more efficiently. However, LONG is >> >> > not supported as the source type of time-based transform (hour, day, >> >> > etc) >> >> > >> >> > I find the previous discussion >> >> > https://github.com/apache/iceberg/issues/417 and Ryan suggested two >> >> > solutions >> >> > >> >> > 1. type promotion from LONG to TIMESTAMP >> >> > 2. custom transform >> >> > >> >> > As I understand it, neither solution has already been implemented yet. >> >> > Is there any progress in either direction? Which solution does the >> >> > community prefer? Any other suggestions are also appreciated. >> >> > >> >> > Thanks, >> >> > Manu
