You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "dannycranmer (via GitHub)" <gi...@apache.org> on 2023/04/12 12:05:40 UTC

[GitHub] [flink-connector-opensearch] dannycranmer commented on pull request #17: [hotfix] Add opensearch.yml to enable flink to find the data

dannycranmer commented on PR #17:
URL: https://github.com/apache/flink-connector-opensearch/pull/17#issuecomment-1505153424

   It makes sense to use the `v3.0` branch instead of the dedicated docs branch. Assuming we are not adding new features for patch releases otherwise the docs may show features that are not actually released. @reswqa unless I misunderstood, I do not think it is the same as what you suggested. Since when we release `v3.1.0` there will be a `v3.1` branch and we still need to update the Flink repo. I understood your proposal to remove the requirement to update the branch in the Flink repo.


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org