[ 
https://issues.apache.org/jira/browse/KNOX-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891334#comment-17891334
 ] 

ASF subversion and git services commented on KNOX-3068:
-------------------------------------------------------

Commit 6fe6a437c07ecd4ac3d34c51b118336db8b5c3ac in knox's branch 
refs/heads/dependabot/maven/org.apache.shiro-shiro-core-1.13.0 from Philip 
Zampino
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=6fe6a437c ]

KNOX-3068 Iceberg REST Catalog service definition (#937)



> Iceberg REST Catalog service definition
> ---------------------------------------
>
>                 Key: KNOX-3068
>                 URL: https://issues.apache.org/jira/browse/KNOX-3068
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 2.1.0
>            Reporter: Philip Zampino
>            Assignee: Philip Zampino
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Need service definition and rewrite rules for Iceberg REST Catalog service. 
> This API is a standard from the Iceberg community which provides a REST API 
> access to the metastore, associated metadata and cloud storage.
> This service definition should be portable to any implementation of the API 
> with appropriate trusted proxy support as required for Knox based proxying.
> See 
> [https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml]
>  for the open api description.
> In conjunction with:
> https://issues.apache.org/jira/browse/KNOX-3016
> https://issues.apache.org/jira/browse/KNOX-3028
> We can support the CLIENT_ID and CLIENT_SECRET issuance, the exchange of 
> those for a JWT token to be used as a bearer token and with this patch the 
> dispatch to a knox trusting REST Catalog implementation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to