flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] lirui-apache opened a new pull request #12682: [FLINK-18320][hive] Fix NOTICE and license files for flink-sql-connec…
Date Tue, 16 Jun 2020 12:29:04 GMT

lirui-apache opened a new pull request #12682:
URL: https://github.com/apache/flink/pull/12682

   …tor-hive 1.2.2 and 2.2.0
   *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
     - 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
   flink-sql-connector-hive depends on `hive-exec` which is a uber jar and doesn't come with
a proper NOTICE file. So we need to find out the artifacts included in `hive-exec`and list
them in our NOTICE file.
   ## Brief change log
     - Update NOTICE file and add licenses for some dependencies.
   ## Verifying this change
   ## Does this pull request potentially affect one of the following parts:
   ## Documentation

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:

View raw message