[
https://issues.apache.org/jira/browse/PHOENIX-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Shi updated PHOENIX-4927:
-
Summary: Disentangle the granularity of guidepost data from the granularity
stored in the client cache
blocking Phoenix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
>
[
https://issues.apache.org/jira/browse/PHOENIX-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaanai updated PHOENIX-5069:
Fix Version/s: 5.0.1
> Use asynchronous refresh to provide non-blocking Phoenix Stats Client Ca
ing Phoenix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Is
nix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Issue Type: Improvement
>
ing Phoenix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Is
to provide non-blocking Phoenix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Is
to provide non-blocking Phoenix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Is
nix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Issue Type: Improvement
>
nix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Issue Type: Improvement
>
nix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Issue Type: Improvement
>
[
https://issues.apache.org/jira/browse/PHOENIX-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Shi reassigned PHOENIX-5069:
Assignee: Bin Shi
> Use asynchronous refresh to provide non-blocking Phoenix Stats Client Ca
ll
causes significant performance penalty and see periodic spikes.
This Jira suggests to use asynchronous refresh mechanism to provide a
non-blocking cache.
> Use asynchronous refresh to provide non-blocking Phoenix Stats
ty and see
periodic spikes.
This Jira suggests to use asynchronous refresh mechanism to fix this and
provide a non-blocking cache.
> Use asynchronous refresh to provide non-blocking Phoenix Stats Client Cache
> ---
>
&g
non-blocking Phoenix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org/jira/browse/PHOENIX-5069
> Project: Phoenix
> Is
provide a non-blocking cache.
> Use asynchronous refresh to provide non-blocking Phoenix Stats Client Cache
> ---
>
> Key: PHOENIX-5069
> URL: https://issues.apache.org
Bin Shi created PHOENIX-5069:
Summary: Use asynchronous refresh to provide non-blocking Phoenix
Stats Client Cache
Key: PHOENIX-5069
URL: https://issues.apache.org/jira/browse/PHOENIX-5069
Project
(See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/352/])
PHOENIX-1581 Client cache not updated after issuing ALTER TABLE statements for
setting phoenix table properties (samarth.jain: rev
46bc9409fa6f6662e6626224171e606860e6c65c)
* phoenix-core/src/main/java/org/apache/phoenix/sc
[
https://issues.apache.org/jira/browse/PHOENIX-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1581:
--
Fix Version/s: 3.3
> Client cache not updated after issuing ALTER TABLE statements
[
https://issues.apache.org/jira/browse/PHOENIX-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1581:
--
Attachment: PHOENIX-1581_3.0.patch
Patch that I will be committing for 3.0
> Client ca
ssue for 3.3 as well. Would you mind porting
this into the 3.0 branch as well?
> Client cache not updated after issuing ALTER TABLE statements for setting
> phoenix table
(See
[https://builds.apache.org/job/Phoenix-master/553/])
PHOENIX-1581 Client cache not updated after issuing ALTER TABLE statements for
setting phoenix table properties (samarth.jain: rev
3e8b685db0b88430cfa0566302e243c96402e3bf)
* phoenix-core/src/main/java/org/apache/phoenix/query/MetaDataMutated.
[
https://issues.apache.org/jira/browse/PHOENIX-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain resolved PHOENIX-1581.
---
Resolution: Fixed
Fix Version/s: 4.3
5.0.0
> Client cache
ylor]
> Client cache not updated after issuing ALTER TABLE statements for setting
> phoenix table properties
> --
>
> Key: PHOENIX-1581
> URL: https://
[
https://issues.apache.org/jira/browse/PHOENIX-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1428#comment-1428
]
James Taylor commented on PHOENIX-1581:
---
+1. Nice work, [~samarthjain].
>
. Thanks!
> Client cache not updated after issuing ALTER TABLE statements for setting
> phoenix table properties
> --
>
> Key: PHOENIX-1581
> URL: https:/
[
https://issues.apache.org/jira/browse/PHOENIX-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1581:
--
Attachment: (was: PHOENIX-1581.patch)
> Client cache not updated after issuing AL
[
https://issues.apache.org/jira/browse/PHOENIX-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1581:
--
Summary: Client cache not updated after issuing ALTER TABLE statements for
setting phoenix
James Taylor created PHOENIX-1490:
-
Summary: Update client cache prior to query compilation
Key: PHOENIX-1490
URL: https://issues.apache.org/jira/browse/PHOENIX-1490
Project: Phoenix
Issue
#52 (See
[https://builds.apache.org/job/Phoenix-4.0-hadoop2/52/])
PHOENIX-1181 client cache fails to update itself after a table was altered from
a diff client (jtaylor: rev 94040d78ffd246bb10af57d5ccb45070c028f59e)
* phoenix-core/src/main/java/org/apache/phoenix/parse/UpsertStatement.java
* pho
oop1 #341 (See
[https://builds.apache.org/job/Phoenix-master-hadoop1/341/])
PHOENIX-1181 client cache fails to update itself after a table was altered from
a diff client (jtaylor: rev c369bbc611a4ceaf9cfb7fc39f6039f193ceccf6)
* phoenix-core/src/main/java/org/apache/phoenix/execute/MutationState.
#193 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/193/])
PHOENIX-1181 client cache fails to update itself after a table was altered from
a diff client (jtaylor: rev 42465628683aa933805e3810fe1a299167344337)
* phoenix-core/src/it/java/org/apache/phoenix/end2end/AlterTableIT.java
* pho
> client cache fails to update itself after a table was altered from a diff
> client
>
>
> Key: PHOENIX-1181
> URL: https://issues.apache.org/jira/b
[
https://issues.apache.org/jira/browse/PHOENIX-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1181:
--
Attachment: PHOENIX-1181-v3.patch
> client cache fails to update itself after a table
9 AM:
Patch that fixes this issue. The issue can occur for a UPSERT or DELETE
statement when auto commit is off. In this case, we were delaying the update of
the client-side cache too long.
was (Author: jamestaylor):
Patch that fixes this issue.
> client cache fails to update itself
[
https://issues.apache.org/jira/browse/PHOENIX-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1181:
--
Attachment: PHOENIX-1181-v2.patch
> client cache fails to update itself after a table
[
https://issues.apache.org/jira/browse/PHOENIX-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1181:
--
Attachment: PHOENIX-1181.patch
Patch that fixes this issue.
> client cache fails to upd
s(diff vms)
>> > which act as storage/retreival endpoints. If I change the schema of a
>> > table, by adding or removing a field, I get errors in the clients that
>> > didn't issue the alter. This is due to an internal client cache that is
>> not
>> > r
Jody Landreneau created PHOENIX-1181:
Summary: client cache fails to update itself after a table was
altered from a diff client
Key: PHOENIX-1181
URL: https://issues.apache.org/jira/browse/PHOENIX-1181
phoenix
> > clients running, which could be on several physical machines(diff vms)
> > which act as storage/retreival endpoints. If I change the schema of a
> > table, by adding or removing a field, I get errors in the clients that
> > didn't issue the alter. This is due to
a
> table, by adding or removing a field, I get errors in the clients that
> didn't issue the alter. This is due to an internal client cache that is not
> refreshed. I note that the connections get their cache from this shared
> client cache so creating/closing connections does not
clients that
didn't issue the alter. This is due to an internal client cache that is not
refreshed. I note that the connections get their cache from this shared
client cache so creating/closing connections does not help.
I would like to add a timed expiration cache also limited by size to
address
42 matches
Mail list logo
