Hi Junbo and all,
Thanks for the detailed proposal. I have a few minor comments about
the REST API:
1. Could we remove the extra "records" segment from the lookup paths?
Point Lookup:
POST /v1/clusters/{cluster}/databases/{database}/tables/{table}/lookup
Prefix Lookup:
POST /v1/clusters/{cluster}/databases/{database}/tables/{table}/prefix-lookup
2. The /records write API does not explicitly define its supported
operation types. My understanding is that Log tables support "append"
only, while primary-key/KV tables support "upsert" and "delete". Could
we document this operation/table compatibility and the error behavior
for unsupported combinations?
3. Could we explicitly support and document the HTTP Authorization
header, especially Authorization: Bearer <token>? This is a common
authentication mechanism for cloud services: Databricks Zerobus and
Confluent REST Proxy use OAuth/OIDC bearer tokens, while Alibaba Cloud
OSS carries signed credentials in the Authorization header [1][2][3].
The Gateway can validate the credential, resolve it to a principal,
and propagate that principal through the existing identity/act-as
mechanism.
[1] https://docs.databricks.com/aws/en/ingestion/zerobus-ingest
[2]
https://docs.confluent.io/platform/current/security/authentication/oauth-oidc/configure-rest-proxy.html
[3]
https://www.alibabacloud.com/help/en/oss/developer-reference/recommend-to-use-signature-version-4
Best regards,
Jark
On Sat, 8 Aug 2026 at 17:04, Keith Lee <[email protected]> wrote:
>
> Hello Junbo,
>
> The usual process for voting is to start a [VOTE] email thread instead of
> initiating it on the same [DISCUSS] thread.
>
> If you'd like to initiate the vote, please start a separate [VOTE] FIP-49:
> Fluss Gateway REST API thread.
>
> Thank you
> Keith
>
> On Fri, Aug 7, 2026 at 11:12 AM Junbo Wang <[email protected]> wrote:
>
> > Hi all,
> >
> > I would like to start the vote for FIP-49: Fluss Gateway REST API [1].
> >
> > The proposal has been actively discussed in the thread [2] — thanks
> > everyone for the thoughtful feedback, which helped shape the scope and
> > clarify the architectural boundaries. It is now ready for a formal vote.
> >
> > The vote will last for at least 72 hours unless there is objection or
> > insufficient votes.
> >
> >
> >
> > [1]
> > https://cwiki.apache.org/confluence/spaces/FLUSS/pages/444334561/FIP-49+Fluss+Gateway+REST+API
> >
> > [2] https://lists.apache.org/thread/s5yjysvoj8o6nxdj49m99hg8yn51tgjw
> >
> >
> > Best regards,
> > Junbo Wang
> >
> >
