[jira] [Assigned] (PHOENIX-5553) Regression for GlobalIndexChecker. It should not be added to transactional views
[ https://issues.apache.org/jira/browse/PHOENIX-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokcen Iskender reassigned PHOENIX-5553: Assignee: Gokcen Iskender > Regression for GlobalIndexChecker. It should not be added to transactional > views > > > Key: PHOENIX-5553 > URL: https://issues.apache.org/jira/browse/PHOENIX-5553 > Project: Phoenix > Issue Type: Bug >Reporter: Gokcen Iskender >Assignee: Gokcen Iskender >Priority: Major > > https://issues.apache.org/jira/browse/PHOENIX-5385 regressed that the > GlobalIndexChecker is added to transactional views -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5553) Regression for GlobalIndexChecker. It should not be added to transactional views
Gokcen Iskender created PHOENIX-5553: Summary: Regression for GlobalIndexChecker. It should not be added to transactional views Key: PHOENIX-5553 URL: https://issues.apache.org/jira/browse/PHOENIX-5553 Project: Phoenix Issue Type: Bug Reporter: Gokcen Iskender https://issues.apache.org/jira/browse/PHOENIX-5385 regressed that the GlobalIndexChecker is added to transactional views -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5552) Hive against Phoenix gets 'Expecting "RPAREN", got "L"' in Tez mode
Toshihiro Suzuki created PHOENIX-5552:
-
Summary: Hive against Phoenix gets 'Expecting "RPAREN", got "L"'
in Tez mode
Key: PHOENIX-5552
URL: https://issues.apache.org/jira/browse/PHOENIX-5552
Project: Phoenix
Issue Type: Bug
Reporter: Toshihiro Suzuki
Assignee: Toshihiro Suzuki
Steps to reproduce are as follows;
1. Create a table that has a BIGINT column in Phoenix:
{code:java}
CREATE TABLE TBL (
COL1 VARCHAR PRIMARY KEY,
COL2 BIGINT
);
{code}
2. Create an external table in Hive against the table created step 1:
{code:java}
create external table tbl (
col1 string,
col2 bigint
)
STORED BY 'org.apache.phoenix.hive.PhoenixStorageHandler'
TBLPROPERTIES (
"phoenix.table.name" = "TBL",
"phoenix.zookeeper.quorum" = ...,
"phoenix.zookeeper.znode.parent" = ...,
"phoenix.zookeeper.client.port" = "2181",
"phoenix.rowkeys" = "COL1",
"phoenix.column.mapping" = "col1:COL1,col2:COL2"
);
{code}
3. Issue a query for the hive table with a condition of the BIGINT column in
Tez mode, but the following error happens:
{code:java}
> select * from tbl where col2 = 100;
Error: java.io.IOException: java.lang.RuntimeException:
org.apache.phoenix.exception.PhoenixParserException: ERROR 603 (42P00): Syntax
error. Unexpected input. Expecting "RPAREN", got "L" at line 1, column 67.
(state=,code=0)
{code}
In this case, the problem is that Hive passes whereClause "col2=100L" (as a
bigint value with 'L') to Phoenix, but phoenix can't accept the bigint value
with 'L', so the syntax error happens.
We need to remove 'L' for bigint values when building phoenix queries.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-5551) Update maven apache parent to version 21
István Tóth created PHOENIX-5551: Summary: Update maven apache parent to version 21 Key: PHOENIX-5551 URL: https://issues.apache.org/jira/browse/PHOENIX-5551 Project: Phoenix Issue Type: Improvement Affects Versions: 5.1.0 Reporter: István Tóth Assignee: István Tóth The Phoenix maven project sets _org.apache:apache_ as maven parent. Most of the functionality of the apache parent is setting up base plugin configuration, including versions for maven plugins. The current pom.xml ignores most of the versions, and sets the plugin versions manually. I propose updating the apache parent artifact to the latest version (21), and removing the explicit plugin version settings where the plugin versions are set by apache parent. This effectively updates some plugins, leaves some at the same version, but does not downgrade any of them. This is the effective plugin version change with this patch: org.apache:apache 14 -> 21 org.apache.maven.plugins:maven-compiler-plugin 3.0 -> 3.7.0 org.apache.maven.plugins:maven-install-plugin 2.5.2 -> 2.5.2 org.apache.maven.plugins:maven-assembly-plugin 2.5.2 -> 3.0.0 org.apache.maven.plugins:maven-failsafe-plugin 2.22.2 -> 2.22.2 org.apache.maven.plugins:maven-dependency-plugin 2.1 -> 3.1.1 org.apache.maven.plugins:maven-shade-plugin 3.1.1 -> 3.1.1 org.apache.maven.plugins:maven-source-plugin 2.2.1 -> 3.0.1 org.apache.maven.plugins:maven-javadoc-plugin 2.9 -> 3.0.1 org.apache.maven.plugins:maven-surefire-plugin 2.22.2 -> 2.22.2 org.apache.maven.plugins:maven-jar-plugin 2.4 -> 3.1.0 org.apache.maven.plugins:maven-site-plugin 3.7.1 -> 3.7.1 org.apache.maven.plugins:maven-gpg-plugin 1.6 -> 1.6 org.apache.maven.plugins:maven-project-info-reports-plugin 3.0.0 -> 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5549) BouncyCastle dependency definition has no effect
[
https://issues.apache.org/jira/browse/PHOENIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
István Tóth reassigned PHOENIX-5549:
Assignee: István Tóth
> BouncyCastle dependency definition has no effect
>
>
> Key: PHOENIX-5549
> URL: https://issues.apache.org/jira/browse/PHOENIX-5549
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: István Tóth
>Assignee: István Tóth
>Priority: Minor
> Attachments: PHOENIX-5549.master.v1.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the master branch, phoenix defines _${bouncycastle.version}_ and uses it
> to set the version of _bcprov-jdk16_ artidact via the DependencyManagement
> mechanism.
> Since the splitting of *phoenix-queryserver* and *phoenix-connector* repos,
> bouncycastle is not used anywhere in the phoenix repo, so this these settings
> have no effect.
> *phoenix-queryserver* and *phoenix-connector* do not declare phoenix as
> parent, and even if they did, they currently refer to phoenix versions where
> these setting were not present.
> Also, the currently defined bouncycastle version is very old.
> Due to these reasons, I propose removing the bouncycastle maven references
> from the phoenix project.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5549) BouncyCastle dependency definition has no effect
[
https://issues.apache.org/jira/browse/PHOENIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
István Tóth updated PHOENIX-5549:
-
Attachment: PHOENIX-5549.master.v1.patch
> BouncyCastle dependency definition has no effect
>
>
> Key: PHOENIX-5549
> URL: https://issues.apache.org/jira/browse/PHOENIX-5549
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: István Tóth
>Priority: Minor
> Attachments: PHOENIX-5549.master.v1.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the master branch, phoenix defines _${bouncycastle.version}_ and uses it
> to set the version of _bcprov-jdk16_ artidact via the DependencyManagement
> mechanism.
> Since the splitting of *phoenix-queryserver* and *phoenix-connector* repos,
> bouncycastle is not used anywhere in the phoenix repo, so this these settings
> have no effect.
> *phoenix-queryserver* and *phoenix-connector* do not declare phoenix as
> parent, and even if they did, they currently refer to phoenix versions where
> these setting were not present.
> Also, the currently defined bouncycastle version is very old.
> Due to these reasons, I propose removing the bouncycastle maven references
> from the phoenix project.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-5550) Scan after local index creation on table having data giving wrong results when long view index id disabled
Rajeshbabu Chintaguntla created PHOENIX-5550:
Summary: Scan after local index creation on table having data
giving wrong results when long view index id disabled
Key: PHOENIX-5550
URL: https://issues.apache.org/jira/browse/PHOENIX-5550
Project: Phoenix
Issue Type: Bug
Reporter: Rajeshbabu Chintaguntla
Assignee: Rajeshbabu Chintaguntla
Fix For: 4.15.0, 5.1.0
After PHOENIX-3547 and PHOENIX-5104 querying after local index creation on the
table having data is failing because of the view index id type mismatches.
The client is sending the SMALLINT as view index id data type.
{noformat}
private PDataType getViewIndexDataType() throws SQLException {
boolean supportsLongViewIndexId =
connection.getQueryServices().getProps().getBoolean(
QueryServices.LONG_VIEW_INDEX_ENABLED_ATTRIB,
QueryServicesOptions.DEFAULT_LONG_VIEW_INDEX_ENABLED);
return supportsLongViewIndexId ? MetaDataUtil.getViewIndexIdDataType()
: MetaDataUtil.getLegacyViewIndexIdDataType();
}
{noformat}
But in the create index api in endpoint impl is considering LONG as view index
id data type.
{noformat}
PDataType dataType =
MetaDataUtil.getViewIndexIdDataType();
Object val = dataType.toObject(seqValue,
PLong.INSTANCE);
byte[] bytes = new byte[dataType.getByteSize() + 1];
dataType.toBytes(val, bytes, 0);
Cell indexIdCell =
PhoenixKeyValueUtil.newKeyValue(cell.getRowArray(),
cell.getRowOffset(), cell.getRowLength(),
cell.getFamilyArray(),
cell.getFamilyOffset(),
cell.getFamilyLength(),
VIEW_INDEX_ID_BYTES, 0,
VIEW_INDEX_ID_BYTES.length,
cell.getTimestamp(), bytes, 0,
bytes.length, cell.getType());
{noformat}
{noformat}
if (indexId != null) {
builder.setViewIndexId(indexId);
builder.setViewIndexIdType(PLong.INSTANCE.getSqlType());
}
{noformat}
Most of the local index tests failing If we set false value to the following
configuration.
phoenix.index.longViewIndex.enabled
false
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5117) Return the count of rows scanned in HBase
[ https://issues.apache.org/jira/browse/PHOENIX-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Feng updated PHOENIX-5117: --- Attachment: PHOENIX-5117-4.x-HBase-1.4-v6.patch > Return the count of rows scanned in HBase > - > > Key: PHOENIX-5117 > URL: https://issues.apache.org/jira/browse/PHOENIX-5117 > Project: Phoenix > Issue Type: New Feature >Affects Versions: 4.14.1 >Reporter: Chen Feng >Assignee: Chen Feng >Priority: Minor > Fix For: 4.15.1, 5.1.1 > > Attachments: PHOENIX-5117-4.x-HBase-1.4-v1.patch, > PHOENIX-5117-4.x-HBase-1.4-v2.patch, PHOENIX-5117-4.x-HBase-1.4-v3.patch, > PHOENIX-5117-4.x-HBase-1.4-v4.patch, PHOENIX-5117-4.x-HBase-1.4-v5.patch, > PHOENIX-5117-4.x-HBase-1.4-v6.patch, PHOENIX-5117-v1.patch > > > HBASE-5980 provides the ability to return the number of rows scanned. Such > metrics should also be returned by Phoenix. > HBASE-21815 is acquired. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (PHOENIX-5527) Unverified index rows should not be deleted due to replication lag
[ https://issues.apache.org/jira/browse/PHOENIX-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR reopened PHOENIX-5527: > Unverified index rows should not be deleted due to replication lag > --- > > Key: PHOENIX-5527 > URL: https://issues.apache.org/jira/browse/PHOENIX-5527 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.14.3 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-5527.master.001.patch, > PHOENIX-5527.master.002.patch, PHOENIX-5527.master.003.patch > > Time Spent: 10m > Remaining Estimate: 0h > > The current default delete time for unverified index rows is 10 minutes. If > an index table row is replicated before its data table row and the > replication row is unverified at the time of replication, it can be deleted > when it is scanned on the destination cluster. To prevent these deletes due > to replication lag issues, we should increase the default time to 7 days. > This value is configurable using the configuration parameter, > phoenix.global.index.row.age.threshold.to.delete.ms. -- This message was sent by Atlassian Jira (v8.3.4#803005)
