Istvan Toth created PHOENIX-5641:
Summary: Decouple phoenix-queryserver from phoenix-core
Key: PHOENIX-5641
URL: https://issues.apache.org/jira/browse/PHOENIX-5641
Project: Phoenix
Issue
[
https://issues.apache.org/jira/browse/PHOENIX-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kadir OZDEMIR updated PHOENIX-5640:
---
Attachment: PHOENIX-5640.4.x-HBase-1.5.001.patch
> Pending disable count should not be
[
https://issues.apache.org/jira/browse/PHOENIX-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kadir OZDEMIR updated PHOENIX-5640:
---
Attachment: (was: PHOENIX-5640.4.x-HBase-1.5.001.patch)
> Pending disable count should
Kadir OZDEMIR created PHOENIX-5640:
--
Summary: Pending disable count should not be increased for rebuild
write failures
Key: PHOENIX-5640
URL: https://issues.apache.org/jira/browse/PHOENIX-5640
+1 (Binding)
- Built from source (4.15.0-HBase-1.3) : OK
- mvn verify : OK
- Did some basic DDL, upserts, deletes, querying, and everything looked
fine : OK
- Did some upgrade testing and created tables, indexes, views, etc. with an
old client, upgraded the client to 4.15 and did some more DDL
As Lars requested, can you please provide your schema(mask confidential
info) and also sample rows where you see duplicate rows and how you are
upserting them.
Agree with William that if the table is salted and you alter salt buckets
then you will see weird behaviour. Recently we had a similar
[
https://issues.apache.org/jira/browse/PHOENIX-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Gupta reassigned PHOENIX-5630:
---
Assignee: Neha Gupta
> MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED
Also, quick question, is your table salted, and have you done anything that
might have altered the salt buckets?
On Wed, Dec 18, 2019 at 7:50 AM la...@apache.org wrote:
> You mean you see multiple rows with the same primary key? I have not see
> this - or heard about this before.
>
> Could you
[
https://issues.apache.org/jira/browse/PHOENIX-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Jacoby updated PHOENIX-5637:
-
Fix Version/s: 4.15.1
5.1.0
> Queries with SCN return expired rows
This is really hard to follow.
I think we should do the same with HBase dependencies in Phoenix that HBase
does with Hadoop dependencies.
That is: We could have a maven module with the specific HBase version
dependent code.
Btw. Tephra does the same... A module for HBase version specific
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-5639:
---
Description:
{code:java}
> CREATE TABLE TEST_5 (ID INTEGER NOT NULL PRIMARY KEY, HOST
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-5639:
---
Priority: Trivial (was: Minor)
> Exception during DROP TABLE CASCADE with VIEW and INDEX
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-5639:
---
Fix Version/s: 4.15.1
> Exception during DROP TABLE CASCADE with VIEW and INDEX
>
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-5639:
---
Summary: Exception during DROP TABLE CASCADE with VIEW and INDEX in
phoenix_sandbox (was:
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl reopened PHOENIX-5639:
> Exception during DROP TABLE CASCADE with VIEW and INDEX
>
You mean you see multiple rows with the same primary key? I have not see this
- or heard about this before.
Could you post your schema?
-- Lars
On Tuesday, December 17, 2019, 7:42:13 PM GMT+1, Francesco Malerba
wrote:
Hi all,
we are having some troubles with Phoenix 4.14 on top of
+1 (binding)
Again... This time I did the following:
- Ran through upgrade and various test scripts using phoenix_sandbox.py (with
PHOENIX-5617 applied). This started with 4.14, created some tables, views, and
indexes, then with a 4.15 client, added/removed views, columns, and indexes,
then
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl resolved PHOENIX-5639.
Resolution: Fixed
NM. This happens only with phoenix_sandbox.py, but not in an actual
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-5639:
---
Fix Version/s: (was: 4.15.1)
> Exception during DROP TABLE CASCADE with VIEW and INDEX
Lars Hofhansl created PHOENIX-5639:
--
Summary: Exception during DROP TABLE CASCADE with VIEW and INDEX
Key: PHOENIX-5639
URL: https://issues.apache.org/jira/browse/PHOENIX-5639
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-5639:
---
Issue Type: Bug (was: Test)
> Exception during DROP TABLE CASCADE with VIEW and INDEX
>
[
https://issues.apache.org/jira/browse/PHOENIX-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-5638:
-
Summary: phoenix-queryserver build system improvements (was:
phoenix-connector build system
Istvan Toth created PHOENIX-5638:
Summary: phoenix-connector build system improvements
Key: PHOENIX-5638
URL: https://issues.apache.org/jira/browse/PHOENIX-5638
Project: Phoenix
Issue Type:
23 matches
Mail list logo
