[jira] [Updated] (HBASE-5773) HtablePool constructor not reading config files in certain cases
[
https://issues.apache.org/jira/browse/HBASE-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-5773:
--
Fix Version/s: 0.96.0
Assignee: Ioan Eugen Stan
HtablePool constructor not reading config files in certain cases
Key: HBASE-5773
URL: https://issues.apache.org/jira/browse/HBASE-5773
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.90.6, 0.92.1, 0.94.1
Reporter: Ioan Eugen Stan
Assignee: Ioan Eugen Stan
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.94.0, 0.96.0
Attachments: different-config-behaviour.90.patch,
different-config-behaviour.90.patch, different-config-behaviour.patch
Creating a HtablePool can issue two behaviour depanding on the constructor
called.
Case 1: loads the configs from hbase-site
public HTablePool() {
this(HBaseConfiguration.create(), Integer.MAX_VALUE);
}
Calling this with null values for Configuration:
public HTablePool(final Configuration config, final int maxSize) {
this(config, maxSize, null, null);
}
will issue:
public HTablePool(final Configuration config, final int maxSize,
final HTableInterfaceFactory tableFactory, PoolType poolType) {
// Make a new configuration instance so I can safely cleanup when
// done with the pool.
this.config = config == null ? new Configuration() : config;
which does not read the hbase-site config files as
HBaseConfiguration.create() does.
I've tracked this problem to all versions of hbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5773) HtablePool constructor not reading config files in certain cases
[
https://issues.apache.org/jira/browse/HBASE-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-5773:
-
Attachment: different-config-behaviour.90.patch
Version I applied to 0.90 branch.
HtablePool constructor not reading config files in certain cases
Key: HBASE-5773
URL: https://issues.apache.org/jira/browse/HBASE-5773
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.90.6, 0.92.1, 0.94.1
Reporter: Ioan Eugen Stan
Priority: Minor
Fix For: 0.92.2, 0.94.0
Attachments: different-config-behaviour.90.patch,
different-config-behaviour.patch
Creating a HtablePool can issue two behaviour depanding on the constructor
called.
Case 1: loads the configs from hbase-site
public HTablePool() {
this(HBaseConfiguration.create(), Integer.MAX_VALUE);
}
Calling this with null values for Configuration:
public HTablePool(final Configuration config, final int maxSize) {
this(config, maxSize, null, null);
}
will issue:
public HTablePool(final Configuration config, final int maxSize,
final HTableInterfaceFactory tableFactory, PoolType poolType) {
// Make a new configuration instance so I can safely cleanup when
// done with the pool.
this.config = config == null ? new Configuration() : config;
which does not read the hbase-site config files as
HBaseConfiguration.create() does.
I've tracked this problem to all versions of hbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5773) HtablePool constructor not reading config files in certain cases
[
https://issues.apache.org/jira/browse/HBASE-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-5773:
-
Attachment: different-config-behaviour.90.patch
hmmm... this version actually compiles. This is what I committed.
HtablePool constructor not reading config files in certain cases
Key: HBASE-5773
URL: https://issues.apache.org/jira/browse/HBASE-5773
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.90.6, 0.92.1, 0.94.1
Reporter: Ioan Eugen Stan
Priority: Minor
Fix For: 0.92.2, 0.94.0
Attachments: different-config-behaviour.90.patch,
different-config-behaviour.90.patch, different-config-behaviour.patch
Creating a HtablePool can issue two behaviour depanding on the constructor
called.
Case 1: loads the configs from hbase-site
public HTablePool() {
this(HBaseConfiguration.create(), Integer.MAX_VALUE);
}
Calling this with null values for Configuration:
public HTablePool(final Configuration config, final int maxSize) {
this(config, maxSize, null, null);
}
will issue:
public HTablePool(final Configuration config, final int maxSize,
final HTableInterfaceFactory tableFactory, PoolType poolType) {
// Make a new configuration instance so I can safely cleanup when
// done with the pool.
this.config = config == null ? new Configuration() : config;
which does not read the hbase-site config files as
HBaseConfiguration.create() does.
I've tracked this problem to all versions of hbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5773) HtablePool constructor not reading config files in certain cases
[
https://issues.apache.org/jira/browse/HBASE-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-5773:
-
Fix Version/s: 0.90.7
Committed to 0.90 branch too.
HtablePool constructor not reading config files in certain cases
Key: HBASE-5773
URL: https://issues.apache.org/jira/browse/HBASE-5773
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.90.6, 0.92.1, 0.94.1
Reporter: Ioan Eugen Stan
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.94.0
Attachments: different-config-behaviour.90.patch,
different-config-behaviour.90.patch, different-config-behaviour.patch
Creating a HtablePool can issue two behaviour depanding on the constructor
called.
Case 1: loads the configs from hbase-site
public HTablePool() {
this(HBaseConfiguration.create(), Integer.MAX_VALUE);
}
Calling this with null values for Configuration:
public HTablePool(final Configuration config, final int maxSize) {
this(config, maxSize, null, null);
}
will issue:
public HTablePool(final Configuration config, final int maxSize,
final HTableInterfaceFactory tableFactory, PoolType poolType) {
// Make a new configuration instance so I can safely cleanup when
// done with the pool.
this.config = config == null ? new Configuration() : config;
which does not read the hbase-site config files as
HBaseConfiguration.create() does.
I've tracked this problem to all versions of hbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5773) HtablePool constructor not reading config files in certain cases
[
https://issues.apache.org/jira/browse/HBASE-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioan Eugen Stan updated HBASE-5773:
---
Fix Version/s: 0.94.1
0.92.2
0.90.7
Status: Patch Available (was: Open)
HtablePool constructor not reading config files in certain cases
Key: HBASE-5773
URL: https://issues.apache.org/jira/browse/HBASE-5773
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.92.1, 0.90.6, 0.94.1
Reporter: Ioan Eugen Stan
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.94.1
Attachments: different-config-behaviour.patch
Creating a HtablePool can issue two behaviour depanding on the constructor
called.
Case 1: loads the configs from hbase-site
public HTablePool() {
this(HBaseConfiguration.create(), Integer.MAX_VALUE);
}
Calling this with null values for Configuration:
public HTablePool(final Configuration config, final int maxSize) {
this(config, maxSize, null, null);
}
will issue:
public HTablePool(final Configuration config, final int maxSize,
final HTableInterfaceFactory tableFactory, PoolType poolType) {
// Make a new configuration instance so I can safely cleanup when
// done with the pool.
this.config = config == null ? new Configuration() : config;
which does not read the hbase-site config files as
HBaseConfiguration.create() does.
I've tracked this problem to all versions of hbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5773) HtablePool constructor not reading config files in certain cases
[
https://issues.apache.org/jira/browse/HBASE-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioan Eugen Stan updated HBASE-5773:
---
Attachment: different-config-behaviour.patch
HtablePool constructor not reading config files in certain cases
Key: HBASE-5773
URL: https://issues.apache.org/jira/browse/HBASE-5773
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.90.6, 0.92.1, 0.94.1
Reporter: Ioan Eugen Stan
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.94.1
Attachments: different-config-behaviour.patch
Creating a HtablePool can issue two behaviour depanding on the constructor
called.
Case 1: loads the configs from hbase-site
public HTablePool() {
this(HBaseConfiguration.create(), Integer.MAX_VALUE);
}
Calling this with null values for Configuration:
public HTablePool(final Configuration config, final int maxSize) {
this(config, maxSize, null, null);
}
will issue:
public HTablePool(final Configuration config, final int maxSize,
final HTableInterfaceFactory tableFactory, PoolType poolType) {
// Make a new configuration instance so I can safely cleanup when
// done with the pool.
this.config = config == null ? new Configuration() : config;
which does not read the hbase-site config files as
HBaseConfiguration.create() does.
I've tracked this problem to all versions of hbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5773) HtablePool constructor not reading config files in certain cases
[
https://issues.apache.org/jira/browse/HBASE-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-5773:
-
Resolution: Fixed
Fix Version/s: (was: 0.94.1)
(was: 0.90.7)
0.94.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk, 0.92, and 0.94 branches. Thanks for the patch Ioan.
HtablePool constructor not reading config files in certain cases
Key: HBASE-5773
URL: https://issues.apache.org/jira/browse/HBASE-5773
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.90.6, 0.92.1, 0.94.1
Reporter: Ioan Eugen Stan
Priority: Minor
Fix For: 0.92.2, 0.94.0
Attachments: different-config-behaviour.patch
Creating a HtablePool can issue two behaviour depanding on the constructor
called.
Case 1: loads the configs from hbase-site
public HTablePool() {
this(HBaseConfiguration.create(), Integer.MAX_VALUE);
}
Calling this with null values for Configuration:
public HTablePool(final Configuration config, final int maxSize) {
this(config, maxSize, null, null);
}
will issue:
public HTablePool(final Configuration config, final int maxSize,
final HTableInterfaceFactory tableFactory, PoolType poolType) {
// Make a new configuration instance so I can safely cleanup when
// done with the pool.
this.config = config == null ? new Configuration() : config;
which does not read the hbase-site config files as
HBaseConfiguration.create() does.
I've tracked this problem to all versions of hbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
