[
https://issues.apache.org/jira/browse/FLINK-30326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646256#comment-17646256
]
Alex Sorokoumov commented on FLINK-30326:
-----------------------------------------
Hey [Jingsong
Lee|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lzljs3620320] ,
I agree that the local filesystem should not be used as storage, and we might
warn users about it. I used the local filesystem only to show that the SQL
client creates a directory structure on disk.
My main point was that the SQL session should not create files on DFS because
it does not necessarily have access. AFAIU, neither SQL gateway nor JM require
DFS credentials for anything but creating schema files on {{{}CREATE TABLE{}}}.
The SQL gateway might run in a different DC and not have access to the DFS at
all.
I suggest that TMs should always create the table files. If
{{{}auto-create=true{}}}, FTS queries would do it on start. If
{{{}auto-create=false{}}}, {{CREATE TABLE}} would submit a job that creates the
directory structure and the schema files.
> SQL Client should not create table directory structure
> ------------------------------------------------------
>
> Key: FLINK-30326
> URL: https://issues.apache.org/jira/browse/FLINK-30326
> Project: Flink
> Issue Type: Bug
> Components: Table Store
> Reporter: Alex Sorokoumov
> Priority: Major
>
> The SQL client creates the schema part of the directory structure for new
> tables. This behavior is incorrect because the SQL client could be attached
> to a SQL gateway that does not necessarily have access to DFSes for all
> catalogs/tables.
> I propose to change the behavior such that FTS sink creates the schema,
> either on the fly if `auto-create=true` or just as a separate job if
> `auto-create=false`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
