While I agree that the configurable separator is the best solution that
balances trade-offs, I don't think that we should move forward when there
has been a veto from the community.
In Iceberg and most ASF communities, votes are intended to confirm
consensus --- not to make decisions. Since we don
+1 (no-binding)
Personally I don't want this change, but I haven't found any other ways to
address issue #10338. It seems that this proposal is the best solution
available.
On Thu, Apr 24, 2025, at 23:36, Zac Blanco wrote:
> +1 (nb)
>
> On 2024/08/20 07:05:45 Robert Stupp wrote:
>> -1 (nb)
>>
+1 (nb)
On 2024/08/20 07:05:45 Robert Stupp wrote:
> -1 (nb)
>
> On 16.08.24 17:46, Dmitri Bourlatchkov wrote:
> > +1 (nb) to the spec change.
> >
> > Cheers,
> > Dmitri.
> >
> > On Fri, Aug 16, 2024 at 4:31 AM Eduard Tudenhöfner
> > wrote:
> >
> > Hey everyone,
> >
> > as I mentioned o
-1 (nb)
On 16.08.24 17:46, Dmitri Bourlatchkov wrote:
+1 (nb) to the spec change.
Cheers,
Dmitri.
On Fri, Aug 16, 2024 at 4:31 AM Eduard Tudenhöfner
wrote:
Hey everyone,
as I mentioned on the DISCUSS thread, this is providing a simple
path forward for users of the V1 APIs (mak
+1 (nb) to the spec change.
Cheers,
Dmitri.
On Fri, Aug 16, 2024 at 4:31 AM Eduard Tudenhöfner
wrote:
> Hey everyone,
>
> as I mentioned on the DISCUSS thread, this is providing a simple path
> forward for users of the V1 APIs (make the namespace separator
> *configurable* instead of *hardcoded
