ecerulm opened a new pull request #13954:
URL: https://github.com/apache/flink/pull/13954
<!--
*Thank you very much for contributing to Apache Flink - we are happy that
you want to help us improve Flink. To help the community review your
contribution in the best possible way, please go through the checklist below,
which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a
hassle. In order to uphold a high standard of quality for code contributions,
while at the same time managing a large number of contributions, we need
contributors to prepare the contributions well, and give reviewers enough
contextual information for the review. Please also understand that
contributions that do not follow this guide will take longer to review and thus
typically be picked up with lower priority by the community.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [JIRA
issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are
made for typos in JavaDoc or documentation files, which need no JIRA issue.
- Name the pull request in the form "[FLINK-XXXX] [component] Title of the
pull request", where *FLINK-XXXX* should be replaced by the actual issue
number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following
this pattern: `[hotfix] [docs] Fix typo in event time introduction` or
`[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes. You can set up Azure Pipelines CI to do that following [this
guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
- Each pull request should address only one issue, not mix up code from
multiple issues.
- Each commit in the pull request has a meaningful commit message
(including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and
this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
This pull request add metadata fields to the Table SQL Filesystem connector
when format=csv.
* `flink.fs.path` field represents the full path to the file that produced
the record
* `flink.fs.basename` field represent the last portion of `flink.fs.path`
## Brief change log
- `FileSystemTableSource` now implements `SupportsReadingMetadata`, and
delegates to the `FileSystemFormatFactory` implementation
- `FileSystemFormatFactory` now inherits from `SupportReadingMetadata`, so
all classes implementing the interface had changed to include at least a dummy
implementation returning no metadata
- `CsvFileSystemFormatFactory` implements `flinks.fs.path` and
`flink.fs.basename`
- `PartitionPathUtils.fillPartitionValueForRecord` modified to account for
the extra metadata fields
- fixed bug on `PushProjectionIntoTableSourceScanRule.onMatch` that forced
the metadata fields n the `CREATE TABLE xx(... yyy VARCHAR METADATA
VIRTUAL,...)` to be declared in a particular order
## Verifying this change
This change added tests and can be verified as follows:
- Added test that checks that `flink.fs.path` in 3 different tables (one
with both metadata fields, one with the same metadata fields in reverse order,
an one with one that particular metadata field)
- Added test that check `flink.fs.basename` in the same way as the one above.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: don't know, I don't think so.
- The runtime per-record code paths (performance sensitive): yes
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? yes
- If yes, how is the feature documented? not documented
----------------------------------------------------------------
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 the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
