github-actions[bot] commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2499294553
This issue has been closed because it has not received any activity in the
last 14 days since being marked as 'stale'
--
This is an automated message from the Apache
github-actions[bot] closed issue #10205: REST Catalog to support custom-catalog
name like HMS/Glue
URL: https://github.com/apache/iceberg/issues/10205
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
github-actions[bot] commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2469334211
This issue has been automatically marked as stale because it has been open
for 180 days with no activity. It will be closed in next 14 days if no further
activity occur
ajantha-bhat commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2112968638
> We can explore supporting alternatives, but I don't feel like making a
change is necessary to address the issue proposed.
Agree.
--
This is an automated message f
jbonofre commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2112965457
I agree with @danielcweeks here with the current REST API. I think it makes
sense to include in the new REST Spec, but no need to be addressed with the
current one.
--
This is
danielcweeks commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2112927398
> Warehouse has a different meaning for catalogs . . .
There is no agreed upon standard for the naming of parts of an identifier,
so while some people will find confusin
jbonofre commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2099809671
@ajantha-bhat i was waiting new review from AWS guys. I will move forward by
creating a branch with jaxrs/open api annotated interfaces to illustrate the
new proposal.
--
This
ajantha-bhat commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2099805039
@jbonofre: I don't see much progress in terms os "new proposal" (no response
from AWS guys), what are the next plans on that?
--
This is an automated message from the Apac
jbonofre commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2099783609
For the context, the `handshake` endpoint of the "new" REST proposal can
provide the catalog name, that's the kind of "configuration exchange". I agree
that `warehouse` is confusi
ajantha-bhat commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2099775221
> I feel like the best way to approach this is to use the warehouse property
to identify what HMS catalog name is being addressed
It is so confusing to use `warehouse`
flyrain commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2099381636
I agreed with @danielcweeks. The Trino client can either pass the catalog
name as a part of url(e.g. ,
`$ENDPOINT/v1/prefix/namespaces/hms_catalog%1Fdb_name/tables/tablename`), or
danielcweeks commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2099361208
@osscm The information passed to the the REST server as part of the
properties is contextual information and is only sent for user sessions. I
wouldn't use this for resolving
osscm commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2099323036
> `iceberg.rest-catalog.warehouse` normally points to a location like
`s3://my_bucket/warehouse_location`. Not sure Trino community is OK to use it
as the catalog name. Even if that
flyrain commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2096945405
I think we are talking about the same thing here. I don't think there is a
need to change the REST spec.
--
This is an automated message from the Apache Git Service.
To respond t
danielcweeks commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2096712578
@flyrain This is already spelled out in the [REST
Spec](https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml#L78).
The warehouse property is just a
flyrain commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2096591207
`iceberg.rest-catalog.warehouse` normally points to a location like
`s3://my_bucket/warehouse_location`. Not sure Trino community is OK to use it
as the catalog name. Even if that
osscm commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2095492489
thanks @flyrain
using `namespace` to include `catalog-name` can also work.
though then what will be the use of `catalog-id`
Though IMO, as Spark and Trino using hive'
flyrain commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2091895186
IIUC, the `catalog-name` is a concept introduced in Hive 3.0 to support one
additional layer on top of `database`. I will consider the multipart namespace
in REST spec is a superse
osscm commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2091666775
I also think catalog-name can be a separate entity.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
jbonofre commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2089794429
@flyrain my understanding of the question is not on the namespace, but more
at catalog level. Maybe I'm wrong :)
--
This is an automated message from the Apache Git Service.
To
flyrain commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2089231268
The multipart namespace in the REST spec can support a use case like
`catalog.db.table`.
--
This is an automated message from the Apache Git Service.
To respond to the message,
jbonofre commented on issue #10205:
URL: https://github.com/apache/iceberg/issues/10205#issuecomment-2085589026
That's the current proposal/discussion:
https://docs.google.com/document/d/1JUtFpdEoa6IAKt1EzJi_re0PUbh56XnfUtRe5WAfl0s/edit?usp=sharing
REST Catalog is not yet a full "spec
22 matches
Mail list logo
