You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "SunShine-1204 (via GitHub)" <gi...@apache.org> on 2023/08/08 13:24:12 UTC
[GitHub] [flink] SunShine-1204 opened a new pull request, #23170: Fix HBaseRowDataLookupFunction HTable instantiation of thread safety problems
SunShine-1204 opened a new pull request, #23170:
URL: https://github.com/apache/flink/pull/23170
<!--
*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
The pull request solved HBaseRowDataLookupFunction HTable thread safety problem, the source code is open () method to initialize a in the class, because in the actual development process in the close basic won't execute () method, result in Ttable cannot be released, Subsequent programs use the same Ttable object, which has serious thread-safety issues. The current workaround is to place the Ttable initialization in the lookup () method and provide a close method for the Ttable to solve the thread-safe problem
## Brief change log
place the Ttable initialization in the lookup () method and provide a close method for the Ttable
## 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): ( no)
- The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
- The serializers: ( no)
- The runtime per-record code paths (performance sensitive): ( no)
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: ( no)
- The S3 file system connector: ( no)
## Documentation
- Does this pull request introduce a new feature? (no)
- 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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [FLINK-32812][Connectors/Hbase]Fix HBaseRowDataLookupFunction HTable instantiation of thread safety problems [flink]
Posted by "snuyanzin (via GitHub)" <gi...@apache.org>.
snuyanzin closed pull request #23170: [FLINK-32812][Connectors/Hbase]Fix HBaseRowDataLookupFunction HTable instantiation of thread safety problems
URL: https://github.com/apache/flink/pull/23170
--
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
[GitHub] [flink] flinkbot commented on pull request #23170: Fix HBaseRowDataLookupFunction HTable instantiation of thread safety problems
Posted by "flinkbot (via GitHub)" <gi...@apache.org>.
flinkbot commented on PR #23170:
URL: https://github.com/apache/flink/pull/23170#issuecomment-1669622788
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "755643940028c7d3dd6e2ca14b37572f1628b699",
"status" : "UNKNOWN",
"url" : "TBD",
"triggerID" : "755643940028c7d3dd6e2ca14b37572f1628b699",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 755643940028c7d3dd6e2ca14b37572f1628b699 UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] SunShine-1204 commented on pull request #23170: [FLINK-32812]Fix HBaseRowDataLookupFunction HTable instantiation of thread safety problems
Posted by "SunShine-1204 (via GitHub)" <gi...@apache.org>.
SunShine-1204 commented on PR #23170:
URL: https://github.com/apache/flink/pull/23170#issuecomment-1675591427
@lincoln-lil Could you help review this PR in your free time?
--
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
[GitHub] [flink] SunShine-1204 commented on pull request #23170: [FLINK-32812]Fix HBaseRowDataLookupFunction HTable instantiation of thread safety problems
Posted by "SunShine-1204 (via GitHub)" <gi...@apache.org>.
SunShine-1204 commented on PR #23170:
URL: https://github.com/apache/flink/pull/23170#issuecomment-1672494032
@zentol @tillrohrmann @StephanEwen @aljoscha
--
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
Re: [PR] [FLINK-32812][Connectors/Hbase]Fix HBaseRowDataLookupFunction HTable instantiation of thread safety problems [flink]
Posted by "snuyanzin (via GitHub)" <gi...@apache.org>.
snuyanzin commented on PR #23170:
URL: https://github.com/apache/flink/pull/23170#issuecomment-1771770285
@SunShine-1204 thanks for your contribution
The Flink HBase connector resides in it's own repository nowadays, if this code change is still relevant, please open the PR in https://github.com/snuyanzin/flink-connector-hbase
--
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