You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/08/27 03:27:07 UTC
[GitHub] [flink] Fin-chan opened a new pull request #13256: [FLINK-18992][table] Fix Table API renameColumns method annotation error
Fin-chan opened a new pull request #13256:
URL: https://github.com/apache/flink/pull/13256
## What is the purpose of the change
Fix Table API renameColumns method annotation error
## Brief change log
example：table.renameColumns($("a").as($("a1")) change to table.renameColumns($("a").as("a1")
## Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / 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:
users@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #13256: [FLINK-18992][table] Fix Table API renameColumns method annotation error
Posted by GitBox <gi...@apache.org>.
flinkbot commented on pull request #13256:
URL: https://github.com/apache/flink/pull/13256#issuecomment-681330991
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "95e574854c6b5901778cf748ef1b4cd4ee4d8e0b",
"status" : "UNKNOWN",
"url" : "TBD",
"triggerID" : "95e574854c6b5901778cf748ef1b4cd4ee4d8e0b",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 95e574854c6b5901778cf748ef1b4cd4ee4d8e0b UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
</details>
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [flink] Fin-chan closed pull request #13256: [FLINK-18992][table] Fix Table API renameColumns method annotation error
Posted by GitBox <gi...@apache.org>.
Fin-chan closed pull request #13256:
URL: https://github.com/apache/flink/pull/13256
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #13256: [FLINK-18992][table] Fix Table API renameColumns method annotation error
Posted by GitBox <gi...@apache.org>.
flinkbot commented on pull request #13256:
URL: https://github.com/apache/flink/pull/13256#issuecomment-681322269
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.
## Automated Checks
Last check on commit 95e574854c6b5901778cf748ef1b4cd4ee4d8e0b (Thu Aug 27 03:29:22 UTC 2020)
**Warnings:**
* No documentation files were touched! Remember to keep the Flink docs up to date!
* **This pull request references an unassigned [Jira ticket](https://issues.apache.org/jira/browse/FLINK-18992).** According to the [code contribution guide](https://flink.apache.org/contributing/contribute-code.html), tickets need to be assigned before starting with the implementation work.
<sub>Mention the bot in a comment to re-run the automated checks.</sub>
## Review Progress
* ❓ 1. The [description] looks good.
* ❓ 2. There is [consensus] that the contribution should go into to Flink.
* ❓ 3. Needs [attention] from.
* ❓ 4. The change fits into the overall [architecture].
* ❓ 5. Overall code [quality] is good.
Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process.<details>
The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required <summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`)
- `@flinkbot approve all` to approve all aspects
- `@flinkbot approve-until architecture` to approve everything until `architecture`
- `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention
- `@flinkbot disapprove architecture` to remove an approval you gave earlier
</details>
----------------------------------------------------------------
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:
users@infra.apache.org