Viraj Jasani created PHOENIX-7398:
-
Summary: New PhoenixStatement API to return row for
Atomic/Conditional Upserts
Key: PHOENIX-7398
URL: https://issues.apache.org/jira/browse/PHOENIX-7398
Project: Ph
[
https://issues.apache.org/jira/browse/PHOENIX-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned PHOENIX-7398:
-
Assignee: Viraj Jasani
> New PhoenixStatement API to return row for Atomic/Conditional
[
https://issues.apache.org/jira/browse/PHOENIX-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-7395:
--
Description:
Phoenix maintains cache of PTable objects, also known as Metadata cache (as a
G
[
https://issues.apache.org/jira/browse/PHOENIX-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned PHOENIX-7395:
-
Assignee: Jing Yu
> Metadata Cache metrics at server and client side
> ---
[
https://issues.apache.org/jira/browse/PHOENIX-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-7386:
--
Fix Version/s: 5.1.4
> Override UPDATE_CACHE_FREQUENCY if table has disabled indexes
> --
Two of the important fixes are merged today so now we are good to start
with 5.2.1 release.
As Istvan also encouraged, please help with 5.2.1 release preparation.
On Mon, Aug 26, 2024 at 10:00 PM Istvan Toth
wrote:
> +1 on the release.
>
> While I would not exactly LIKE to be RM, I may be able
[
https://issues.apache.org/jira/browse/PHOENIX-7394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved PHOENIX-7394.
---
Resolution: Fixed
> MaxPhoenixColumnSizeExceededException should not print rowkey
> ---
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei reassigned PHOENIX-7397:
-
Assignee: chenglei
> Optimize ClientAggregatePlan/ClientScanPlan when inner query is UnionPlan
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-7397:
--
Summary: Optimize ClientAggregatePlan/ClientScanPlan when inner query is
UnionPlan (was: Optimize Cl
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-7397:
--
Description:
A common use case of union all is to union multiple homogeneous tables and then
further
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-7397:
--
Description:
A common use case of union all is to union multiple homogeneous tables and then
further
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-7397:
--
Description:
A common use case of union all is to union multiple homogeneous tables and then
further
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-7397:
--
Description:
A common use case of union all is to union multiple homogeneous tables and then
further
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-7397:
--
Description:
A common use case of union all is to union multiple homogeneous tables and then
further
[
https://issues.apache.org/jira/browse/PHOENIX-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved PHOENIX-7393.
---
Resolution: Fixed
> Update transitive dependency of woodstox-core to 5.4.0
> --
[
https://issues.apache.org/jira/browse/PHOENIX-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-7393:
--
Fix Version/s: 5.2.1
5.3.0
5.1.4
> Update transitive de
[
https://issues.apache.org/jira/browse/PHOENIX-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-7397:
--
Description:
A common use case of union all is to union multiple homogeneous tables and then
further
chenglei created PHOENIX-7397:
-
Summary: Optimize ClientAggregatePlan/ClientScanPlan when inner
query plan is UnionPlan
Key: PHOENIX-7397
URL: https://issues.apache.org/jira/browse/PHOENIX-7397
Project: P
[
https://issues.apache.org/jira/browse/PHOENIX-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Krishna Dara reassigned PHOENIX-7343:
--
Assignee: Hari Krishna Dara
> Support for complex types in CDC
> ---
On second thought that makes sense, we didn't touch the V1 driver when
porting to Spark3.
Your suggestion sounds good.
On Thu, Aug 29, 2024 at 11:53 AM Rejeb Ben Rejeb
wrote:
> Yes, it's correct.
>
> Le jeu. 29 août 2024 à 11:12, Istvan Toth a
> écrit :
>
> > So the V1 code in Spark 3 still be
Yes, it's correct.
Le jeu. 29 août 2024 à 11:12, Istvan Toth a
écrit :
> So the V1 code in Spark 3 still behaves as Spark2 does, which is different
> from the V2 in Spark3.
> Do I understand correctly ?
>
> On Thu, Aug 29, 2024 at 10:28 AM Rejeb Ben Rejeb
> wrote:
>
> > Sorry, I explained it ba
So the V1 code in Spark 3 still behaves as Spark2 does, which is different
from the V2 in Spark3.
Do I understand correctly ?
On Thu, Aug 29, 2024 at 10:28 AM Rejeb Ben Rejeb
wrote:
> Sorry, I explained it badly, I meant spark3 will support both Append and
> Overwrite mode and both will behave t
Sorry, I explained it badly, I meant spark3 will support both Append and
Overwrite mode and both will behave the same way.
I agree that the new one is correct and that we shouldn't add support for
Overwrite mode.
I think it is a better option than keeping old V1 code.
I don't think that it is possi
On Wed, Aug 28, 2024 at 2:49 PM Rejeb Ben Rejeb
wrote:
> Le mer. 28 août 2024 à 10:17, Istvan Toth a
> écrit :
>
> > On Mon, Aug 26, 2024 at 1:59 PM Rejeb Ben Rejeb >
> > wrote:
> >
> > > Hi,
> > >
> > > REMOVE DATASOURCE V1:
> > > After removing V1 code, it is possible to configure V1 name as
24 matches
Mail list logo
