[jira] [Assigned] (PHOENIX-6407) phoenixdb for Python silently ignores placeholders < placeholder arguments
[
https://issues.apache.org/jira/browse/PHOENIX-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richárd Antal reassigned PHOENIX-6407:
--
Assignee: Richárd Antal
> phoenixdb for Python silently ignores placeholders < placeholder arguments
> --
>
> Key: PHOENIX-6407
> URL: https://issues.apache.org/jira/browse/PHOENIX-6407
> Project: Phoenix
> Issue Type: Bug
> Components: python
>Affects Versions: 5.1.0
>Reporter: Ben DeMott
>Assignee: Richárd Antal
>Priority: Minor
> Labels: phoenixdb
>
> The `phoenixdb` driver for Python does not alert the user to excess arguments
> that are not represented by placeholders.
> *Example 1*, fewer arguments than placeholders raise exception (works as
> expected)
>
> {code:java}
> cursor.execute("UPSERT INTO users VALUES (?, ?, ?)", (123, 'John Doe')) {code}
> {noformat}
> phoenixdb.errors.ProgrammingError: ('Number of columns upserting must match
> number of values. Numbers of columns: 3. Number of values: 4
> tableName=USERS', 1020, '42Y60', None){noformat}
> *Example 2,* additional arguments than placeholders is silently ignored
> {code:java}
> cursor.execute("UPSERT INTO users VALUES (?, ?)", (123, 'John Doe',
> 'admin')){code}
> The program should generate a similar error to the one above, that the
> columns need to match the replacements.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6461) sqlline-thin does not include slf4j logging backend
[ https://issues.apache.org/jira/browse/PHOENIX-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richárd Antal resolved PHOENIX-6461. Fix Version/s: queryserver-6.0.0 Assignee: Richárd Antal Resolution: Fixed > sqlline-thin does not include slf4j logging backend > --- > > Key: PHOENIX-6461 > URL: https://issues.apache.org/jira/browse/PHOENIX-6461 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Reporter: Istvan Toth >Assignee: Richárd Antal >Priority: Major > Fix For: queryserver-6.0.0 > > > The Avatica client JAR that we use in the phoenix thin client JAR does not > include and sfl4j backend. > This in itself is not a problem, as it allows dependent project to use their > preferred backend. > However, we are not adding a backend in the sqlline-thin script either, which > results in any log messages being dropped. > We should add a log implementation in the sqlline-thin script to the > classpath. > Probably slf4j-simple would be the best choice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6506) Tenant Connection is not able to access/validate Global Sequences
[ https://issues.apache.org/jira/browse/PHOENIX-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Khurana updated PHOENIX-6506: Attachment: PHOENIX-6506.patch > Tenant Connection is not able to access/validate Global Sequences > - > > Key: PHOENIX-6506 > URL: https://issues.apache.org/jira/browse/PHOENIX-6506 > Project: Phoenix > Issue Type: Bug >Reporter: Lokesh Khurana >Assignee: Lokesh Khurana >Priority: Major > Attachments: PHOENIX-6506-test.patch, PHOENIX-6506.patch > > > In our test environment we were using sequence(created using global > connection) in our Table, recently we updated that table to be MULTI_TENANT > and both types of connections (tenant and global) are needs to upsert data > into Table. > Tenant connections are not able to upsert data into table as it is not able > to validate sequence and getting SequenceNotFoundException. > Adding patch with Test failing due to same scenario. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6507) DistinctAggregatingResultIterator should keep original tuple order of the AggregatingResultIterator
chenglei created PHOENIX-6507: - Summary: DistinctAggregatingResultIterator should keep original tuple order of the AggregatingResultIterator Key: PHOENIX-6507 URL: https://issues.apache.org/jira/browse/PHOENIX-6507 Project: Phoenix Issue Type: Bug Affects Versions: 5.1.2, 4.16.1 Reporter: chenglei Fix For: 4.17.0, 5.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
