ankitjain64 commented on a change in pull request #1328:
URL: https://github.com/apache/phoenix/pull/1328#discussion_r724465972
##########
File path: phoenix-core/src/main/java/org/apache/phoenix/util/ServerUtil.java
##########
@@ -328,7 +337,16 @@ public void shutdown() {
@Override
public HTableInterface getTable(ImmutableBytesPtr tablename,
ExecutorService pool)
throws IOException {
- return getConnection().getTable(tablename.copyBytesIfNecessary(),
pool);
+ ClusterConnection connection = null;
+ try {
+ connection = getConnection();
+ return connection.getTable(tablename.copyBytesIfNecessary(),
pool);
+ }catch (IllegalArgumentException e) {
Review comment:
@tkhurana I also thought of doing exactly this while making the above
change. But while checking the underlying hbase implementations, when we pass
`pool = null` this
[getDefaultExecutor](https://github.com/apache/hbase/blob/branch-1.4/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java#L213)
is called
[here](https://github.com/apache/hbase/blob/branch-1.4/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java#L320)
to create the ThreadPool, but in the scenario when no pool object is passed
like in our case on [line
320](https://github.com/apache/phoenix/pull/1328/files#diff-28b6df839a384471211d620c7845ea2a40c8ef67e35966a07122bb4f8938086dR320)
the underlying ThreadPool creation is different
[Link](https://github.com/apache/phoenix/pull/1328/files#diff-28b6df839a384471211d620c7845ea2a40c8ef67e35966a07122bb4f8938086dR320)
and
[getBatchPool](https://github.com/apache/hbase/blob/branch-1.4/hbase-client/src/main/java/org/apache/hadoop/hbase/client/C
onnectionManager.java#L827) is called. That's why I did merge those two
function calls.
Please let me know if I am missing anything and you still think we should
make the above refactor. Thanks
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
