[jira] [Comment Edited] (PHOENIX-6983) Add hint to disable server merges for uncovered index queries

[ https://issues.apache.org/jira/browse/PHOENIX-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737302#comment-17737302 ] Lars Hofhansl edited comment on PHOENIX-6983 at 6/26/23 5:50 PM: - isn't

[jira] [Commented] (PHOENIX-6983) Add hint to disable server merges for uncovered index queries

[ https://issues.apache.org/jira/browse/PHOENIX-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737302#comment-17737302 ] Lars Hofhansl commented on PHOENIX-6983: isn't this the same as hinting not to use the index in

[jira] (PHOENIX-792) Support UPSERT SET command

[ https://issues.apache.org/jira/browse/PHOENIX-792 ] Lars Hofhansl deleted comment on PHOENIX-792: --- was (Author: JIRAUSER297473): Informative, for more info visit this [Blog|https://techlarapoint.com/]. > Support UPSERT SET command >

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516359#comment-17516359 ] Lars Hofhansl commented on PHOENIX-6671: Or just this (checks HBase version), assuming this

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516185#comment-17516185 ] Lars Hofhansl commented on PHOENIX-6671: With HBASE-26869 and HBASE-26812 committed I think we

[jira] [Commented] (PHOENIX-6678) Dbeaver jdbc connetion for Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515672#comment-17515672 ] Lars Hofhansl commented on PHOENIX-6678: The email list

[jira] [Commented] (PHOENIX-6678) Dbeaver jdbc connetion for Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515014#comment-17515014 ] Lars Hofhansl commented on PHOENIX-6678: It is better to ask this on the mailing lists.

[jira] [Commented] (PHOENIX-6677) Parallelism within a batch of mutations

[ https://issues.apache.org/jira/browse/PHOENIX-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515013#comment-17515013 ] Lars Hofhansl commented on PHOENIX-6677: I never quite understood why Phoenix needs to break up

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510820#comment-17510820 ] Lars Hofhansl commented on PHOENIX-6671: Hi [~comnetwork] , thanks for working out the patch.

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510025#comment-17510025 ] Lars Hofhansl commented on PHOENIX-6671: Note that HBASE-26869 *does* fix the problem. So now

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509610#comment-17509610 ] Lars Hofhansl commented on PHOENIX-6671: Cool. Thanks for checking! I'd vote to get it in then.

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509306#comment-17509306 ] Lars Hofhansl commented on PHOENIX-6671: We need to be careful with this in production

[jira] [Comment Edited] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509306#comment-17509306 ] Lars Hofhansl edited comment on PHOENIX-6671 at 3/19/22, 4:52 PM: -- We

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509105#comment-17509105 ] Lars Hofhansl commented on PHOENIX-6671: [~kozdemir], [~apurtell], FYI. > Avoid

[jira] [Commented] (PHOENIX-6671) Avoid ShortCirtuation Coprocessor Connection with HBase 2.x

[ https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509104#comment-17509104 ] Lars Hofhansl commented on PHOENIX-6671: One line change. Just get a regular Connection. >

[jira] [Commented] (PHOENIX-6501) Use batching when joining data table rows with uncovered global index rows

[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505073#comment-17505073 ] Lars Hofhansl commented on PHOENIX-6501: With the latest version of this patch the query

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502747#comment-17502747 ] Lars Hofhansl commented on PHOENIX-6458: See: HBASE-26812 > Using global indexes for queries

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502729#comment-17502729 ] Lars Hofhansl commented on PHOENIX-6458: I think I figured out the problem... It's an HBase 2.x

[jira] [Comment Edited] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502660#comment-17502660 ] Lars Hofhansl edited comment on PHOENIX-6458 at 3/8/22, 1:33 AM: - Sorry

[jira] [Comment Edited] (PHOENIX-6501) Use batching when joining data table rows with uncovered global index rows

[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502661#comment-17502661 ] Lars Hofhansl edited comment on PHOENIX-6501 at 3/8/22, 1:32 AM: - Sorry

[jira] [Comment Edited] (PHOENIX-6501) Use batching when joining data table rows with uncovered global index rows

[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502661#comment-17502661 ] Lars Hofhansl edited comment on PHOENIX-6501 at 3/8/22, 1:32 AM: - Sorry

[jira] [Commented] (PHOENIX-6501) Use batching when joining data table rows with uncovered global index rows

[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502661#comment-17502661 ] Lars Hofhansl commented on PHOENIX-6501: Sorry - doing too many things as the same time - the

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502660#comment-17502660 ] Lars Hofhansl commented on PHOENIX-6458: Sorry all... I'm an idiot. I ran the last queries with

[jira] [Commented] (PHOENIX-6501) Use batching when joining data table rows with uncovered index rows

[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502624#comment-17502624 ] Lars Hofhansl commented on PHOENIX-6501: As discussed in PHOENIX-6458, there was an issue with

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502599#comment-17502599 ] Lars Hofhansl commented on PHOENIX-6458: [~kozdemir] and I talked offline. Looks like creating

[jira] [Commented] (PHOENIX-6501) Use batching when joining data table rows with uncovered index rows

[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502556#comment-17502556 ] Lars Hofhansl commented on PHOENIX-6501: That might be a bit tricky. I loaded the TPCH lineitem

[jira] [Commented] (PHOENIX-6501) Use batching when joining data table rows with uncovered index rows

[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502541#comment-17502541 ] Lars Hofhansl commented on PHOENIX-6501: Testing the attached patch. Running a query on a table

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502524#comment-17502524 ] Lars Hofhansl commented on PHOENIX-6458: I agree. I do not understand either. It's as if the

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502488#comment-17502488 ] Lars Hofhansl commented on PHOENIX-6458: OK... I see 200410 open StoreScanners. So looks like

[jira] [Comment Edited] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502468#comment-17502468 ] Lars Hofhansl edited comment on PHOENIX-6458 at 3/7/22, 6:09 PM: -

[jira] [Comment Edited] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502468#comment-17502468 ] Lars Hofhansl edited comment on PHOENIX-6458 at 3/7/22, 6:08 PM: -

[jira] [Comment Edited] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502468#comment-17502468 ] Lars Hofhansl edited comment on PHOENIX-6458 at 3/7/22, 5:59 PM: -

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502468#comment-17502468 ] Lars Hofhansl commented on PHOENIX-6458: Trying now. There's something pretty terrible going

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502458#comment-17502458 ] Lars Hofhansl commented on PHOENIX-6458: I'll verify today - and my apologies that I didn't

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501614#comment-17501614 ] Lars Hofhansl commented on PHOENIX-6458: Hmm... Doesn't quite seem to work: {code:java} >

[jira] [Commented] (PHOENIX-6636) Replace bundled log4j libraries with reload4j

[ https://issues.apache.org/jira/browse/PHOENIX-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499082#comment-17499082 ] Lars Hofhansl commented on PHOENIX-6636: Thanks. Works fine now. > Replace bundled log4j

[jira] [Commented] (PHOENIX-6636) Replace bundled log4j libraries with reload4j

[ https://issues.apache.org/jira/browse/PHOENIX-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498354#comment-17498354 ] Lars Hofhansl commented on PHOENIX-6636: (y) > Replace bundled log4j libraries with reload4j >

[jira] [Comment Edited] (PHOENIX-6636) Replace bundled log4j libraries with reload4j

[ https://issues.apache.org/jira/browse/PHOENIX-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498305#comment-17498305 ] Lars Hofhansl edited comment on PHOENIX-6636 at 2/25/22, 9:26 PM: --

[jira] [Comment Edited] (PHOENIX-6636) Replace bundled log4j libraries with reload4j

[ https://issues.apache.org/jira/browse/PHOENIX-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498305#comment-17498305 ] Lars Hofhansl edited comment on PHOENIX-6636 at 2/25/22, 8:50 PM: --

[jira] [Commented] (PHOENIX-6636) Replace bundled log4j libraries with reload4j

[ https://issues.apache.org/jira/browse/PHOENIX-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498305#comment-17498305 ] Lars Hofhansl commented on PHOENIX-6636: Hmm... Getting this now when starting Phoenix (hbase

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498285#comment-17498285 ] Lars Hofhansl commented on PHOENIX-6458: (y) Awesome > Using global indexes for queries with

[jira] [Commented] (PHOENIX-6458) Using global indexes for queries with uncovered columns

[ https://issues.apache.org/jira/browse/PHOENIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17497945#comment-17497945 ] Lars Hofhansl commented on PHOENIX-6458: [~kozdemir] This should go into the 5.1 branch as

[jira] [Commented] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490481#comment-17490481 ] Lars Hofhansl commented on PHOENIX-6647: Now that I spent a 1/2 looking at this, the cost

[jira] [Commented] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490038#comment-17490038 ] Lars Hofhansl commented on PHOENIX-6647: But that doesn't work well for sorting... I'll leave

[jira] [Commented] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490014#comment-17490014 ] Lars Hofhansl commented on PHOENIX-6647: -v2 is better. Takes increased size and significant

[jira] [Comment Edited] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489869#comment-17489869 ] Lars Hofhansl edited comment on PHOENIX-6647 at 2/10/22, 5:03 AM: -- Ah.

[jira] [Commented] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489869#comment-17489869 ] Lars Hofhansl commented on PHOENIX-6647: Ah. Can't help it. Here's a change that fixes it for

[jira] [Comment Edited] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489844#comment-17489844 ] Lars Hofhansl edited comment on PHOENIX-6647 at 2/9/22, 10:32 PM: -- I

[jira] [Commented] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489844#comment-17489844 ] Lars Hofhansl commented on PHOENIX-6647: I do have the cost based optimizer enabled, which I

[jira] [Commented] (PHOENIX-6647) A local index should not be chosen for a full scan if that scan is not covered by the index.

[ https://issues.apache.org/jira/browse/PHOENIX-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489841#comment-17489841 ] Lars Hofhansl commented on PHOENIX-6647: The planner determines that there are fewer bytes to

[jira] [Commented] (PHOENIX-6615) The Tephra transaction processor cannot be loaded anymore.

[ https://issues.apache.org/jira/browse/PHOENIX-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470170#comment-17470170 ] Lars Hofhansl commented on PHOENIX-6615: Thanks! Just approved the PR. Happy to merge unless

[jira] [Commented] (PHOENIX-6615) The Tephra transaction processor cannot be loaded anymore.

[ https://issues.apache.org/jira/browse/PHOENIX-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463377#comment-17463377 ] Lars Hofhansl commented on PHOENIX-6615: I guess the breakage was hard to notice, since the

[jira] [Commented] (PHOENIX-6615) The Tephra transaction processor cannot be loaded anymore.

[ https://issues.apache.org/jira/browse/PHOENIX-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463376#comment-17463376 ] Lars Hofhansl commented on PHOENIX-6615: Thanks [~stoty] . I agree the bitrot is around

[jira] [Commented] (PHOENIX-6615) The Tephra transaction processor cannot be loaded anymore.

[ https://issues.apache.org/jira/browse/PHOENIX-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463016#comment-17463016 ] Lars Hofhansl commented on PHOENIX-6615: I guess something like this is what you wanted...

[jira] [Commented] (PHOENIX-6064) Make Tephra support optional

[ https://issues.apache.org/jira/browse/PHOENIX-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463007#comment-17463007 ] Lars Hofhansl commented on PHOENIX-6064: Turns out this actually break Tephra completely and

[jira] [Commented] (PHOENIX-6608) DISCUSS: Rethink MapReduce split generation

[ https://issues.apache.org/jira/browse/PHOENIX-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17457296#comment-17457296 ] Lars Hofhansl commented on PHOENIX-6608: Yeah, if each worker uses a JDBC client and replans

[jira] (PHOENIX-6604) Allow using indexes for wildcard topN queries on salted tables

[ https://issues.apache.org/jira/browse/PHOENIX-6604 ] Lars Hofhansl deleted comment on PHOENIX-6604: was (Author: githubbot): lhofhansl edited a comment on pull request #1362: URL:

[jira] [Commented] (PHOENIX-6608) DISCUSS: Rethink MapReduce split generation

[ https://issues.apache.org/jira/browse/PHOENIX-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455885#comment-17455885 ] Lars Hofhansl commented on PHOENIX-6608: What kind of worker? Is that some custom worker with a

[jira] [Commented] (PHOENIX-6604) Index not used for wildcard topN query on salted table

[ https://issues.apache.org/jira/browse/PHOENIX-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453452#comment-17453452 ] Lars Hofhansl commented on PHOENIX-6604: Is anyone looking at Jira anyore? > Index not used

[jira] [Commented] (PHOENIX-6604) Index not used for wildcard topN query on salted table

[ https://issues.apache.org/jira/browse/PHOENIX-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17449277#comment-17449277 ] Lars Hofhansl commented on PHOENIX-6604: With a test. (Can't run tests locally, but I think

[jira] [Commented] (PHOENIX-6604) Index not used for wildcard topN query on salted table

[ https://issues.apache.org/jira/browse/PHOENIX-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448966#comment-17448966 ] Lars Hofhansl commented on PHOENIX-6604: Actually attached patch fixes it for me. Should be

[jira] [Commented] (PHOENIX-6604) Index not used for wildcard topN query on salted table

[ https://issues.apache.org/jira/browse/PHOENIX-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448958#comment-17448958 ] Lars Hofhansl commented on PHOENIX-6604: The same happens with a fully covered global index.

[jira] [Commented] (PHOENIX-6604) Local index not used for wildcard topN query on salted table

[ https://issues.apache.org/jira/browse/PHOENIX-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448953#comment-17448953 ] Lars Hofhansl commented on PHOENIX-6604: I likely won't have time to track it down. Just

[jira] [Commented] (PHOENIX-6444) Extend Cell Tags to Delete object for Indexer coproc

[ https://issues.apache.org/jira/browse/PHOENIX-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352930#comment-17352930 ] Lars Hofhansl commented on PHOENIX-6444: If the master change applies (mostly) cleanly, we can

[jira] [Commented] (PHOENIX-5639) Exception during DROP TABLE CASCADE with VIEW and INDEX in phoenix_sandbox

[ https://issues.apache.org/jira/browse/PHOENIX-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352006#comment-17352006 ] Lars Hofhansl commented on PHOENIX-5639: Removing release targets of a 18 months old issue. >

[jira] [Commented] (PHOENIX-6437) Delete marker for parent-child rows does not get replicated via SystemCatalogWALEntryFilter

[ https://issues.apache.org/jira/browse/PHOENIX-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352003#comment-17352003 ] Lars Hofhansl commented on PHOENIX-6437: I cherry-picked it into branch-5.1. > Delete marker

[jira] [Commented] (PHOENIX-6435) Fix ViewTTLIT test flapper

[ https://issues.apache.org/jira/browse/PHOENIX-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351996#comment-17351996 ] Lars Hofhansl commented on PHOENIX-6435: Done. > Fix ViewTTLIT test flapper >

[jira] [Commented] (PHOENIX-6435) Fix ViewTTLIT test flapper

[ https://issues.apache.org/jira/browse/PHOENIX-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351995#comment-17351995 ] Lars Hofhansl commented on PHOENIX-6435: I'm going to cherry-pick this into 5.1. > Fix

[jira] [Commented] (PHOENIX-6437) Delete marker for parent-child rows does not get replicated via SystemCatalogWALEntryFilter

[ https://issues.apache.org/jira/browse/PHOENIX-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351994#comment-17351994 ] Lars Hofhansl commented on PHOENIX-6437: What about 5.1? Since it's in 4.16.2 it should be in

[jira] [Commented] (PHOENIX-6447) Add support for SYSTEM.CHILD_LINK table in systemcatalogwalentryfilter

[ https://issues.apache.org/jira/browse/PHOENIX-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351991#comment-17351991 ] Lars Hofhansl commented on PHOENIX-6447: I cherry-picked the change in. All done. All good :)

[jira] [Commented] (PHOENIX-6447) Add support for SYSTEM.CHILD_LINK table in systemcatalogwalentryfilter

[ https://issues.apache.org/jira/browse/PHOENIX-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351988#comment-17351988 ] Lars Hofhansl commented on PHOENIX-6447: [~sandeep.pal] did you get a chance yet? If the change

[jira] [Commented] (PHOENIX-6435) Fix ViewTTLIT test flapper

[ https://issues.apache.org/jira/browse/PHOENIX-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344834#comment-17344834 ] Lars Hofhansl commented on PHOENIX-6435: 5.1.2? (branch 5.1) > Fix ViewTTLIT test flapper >

[jira] [Commented] (PHOENIX-6420) Wrong result when conditional and regular upserts are passed in the same commit batch

[ https://issues.apache.org/jira/browse/PHOENIX-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344833#comment-17344833 ] Lars Hofhansl commented on PHOENIX-6420: Looks like this should be merged into branch 5.1 (for

[jira] [Commented] (PHOENIX-6395) Reusing Connection instance object instead of creating everytime in PhoenixAccessController class.

[ https://issues.apache.org/jira/browse/PHOENIX-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344831#comment-17344831 ] Lars Hofhansl commented on PHOENIX-6395: What about branch 5.1 (5.1.2)? > Reusing Connection

[jira] [Commented] (PHOENIX-6271) Effective DDL generated by SchemaExtractionTool should maintain the order of PK and other columns

[ https://issues.apache.org/jira/browse/PHOENIX-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344830#comment-17344830 ] Lars Hofhansl commented on PHOENIX-6271: Looks like this be merged into 5.1.2 (branch 5.1) as

[jira] [Commented] (PHOENIX-6227) Option for DDL changes to export to external schema repository

[ https://issues.apache.org/jira/browse/PHOENIX-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344826#comment-17344826 ] Lars Hofhansl commented on PHOENIX-6227: Should this be in 5.1.2 as well? > Option for DDL

[jira] [Commented] (PHOENIX-6085) Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the upgrade path

[ https://issues.apache.org/jira/browse/PHOENIX-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344825#comment-17344825 ] Lars Hofhansl commented on PHOENIX-6085: And what about Phoenix 5.1.2? (branch 5.1) > Remove

[jira] [Commented] (PHOENIX-6447) Add support for SYSTEM.CHILD_LINK table in systemcatalogwalentryfilter

[ https://issues.apache.org/jira/browse/PHOENIX-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344242#comment-17344242 ] Lars Hofhansl commented on PHOENIX-6447: Should this one be in branch-5.1 (i.e. Phoenix 5.1.2)?

[jira] [Commented] (PHOENIX-6444) Extend Cell Tags to Delete object for Indexer coproc

[ https://issues.apache.org/jira/browse/PHOENIX-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344244#comment-17344244 ] Lars Hofhansl commented on PHOENIX-6444: What about branch-5.1 (Phoenix 5.1.2)? > Extend Cell

[jira] [Commented] (PHOENIX-6454) Add feature to SchemaTool to get the DDL in specification mode

[ https://issues.apache.org/jira/browse/PHOENIX-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344239#comment-17344239 ] Lars Hofhansl commented on PHOENIX-6454: Should this one be in branch-5.1 (i.e. Phoenix 5.1.2)

[jira] [Commented] (PHOENIX-6457) Optionally store schema version string in SYSTEM.CATALOG

[ https://issues.apache.org/jira/browse/PHOENIX-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344237#comment-17344237 ] Lars Hofhansl commented on PHOENIX-6457: I think. Thanks [~gjacoby] > Optionally store schema

[jira] [Commented] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329519#comment-17329519 ] Lars Hofhansl commented on PHOENIX-6434: It's resolved, but I do not see it in the 5.1 branch,

[jira] [Commented] (PHOENIX-6449) Cannot start minicluster in github CI check for connectors

[ https://issues.apache.org/jira/browse/PHOENIX-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329305#comment-17329305 ] Lars Hofhansl commented on PHOENIX-6449: (y) > Cannot start minicluster in github CI check for

[jira] [Commented] (PHOENIX-6449) Cannot start minicluster in github CI check for connectors

[ https://issues.apache.org/jira/browse/PHOENIX-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325190#comment-17325190 ] Lars Hofhansl commented on PHOENIX-6449: We just ran into something similar with Trino when

[jira] [Commented] (PHOENIX-6448) ConnectionQueryServicesImpl init failure may cause Full GC.

[ https://issues.apache.org/jira/browse/PHOENIX-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325189#comment-17325189 ] Lars Hofhansl commented on PHOENIX-6448: With [~kadir]'s client paced iteration, do we even

[jira] [Commented] (PHOENIX-6445) Wrong query plans with functions

[ https://issues.apache.org/jira/browse/PHOENIX-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17322460#comment-17322460 ] Lars Hofhansl commented on PHOENIX-6445: Four. This should be a valid query: {code} > explain

[jira] [Comment Edited] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321841#comment-17321841 ] Lars Hofhansl edited comment on PHOENIX-6434 at 4/15/21, 1:48 AM: -- See

[jira] [Commented] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321841#comment-17321841 ] Lars Hofhansl commented on PHOENIX-6434: See PHOENIX-6445 (back to vacation now) > Secondary

[jira] [Commented] (PHOENIX-6445) Wrong query plans with functions

[ https://issues.apache.org/jira/browse/PHOENIX-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321840#comment-17321840 ] Lars Hofhansl commented on PHOENIX-6445: Three. Final count is missing. {code} > explain select

[jira] [Commented] (PHOENIX-6445) Wrong query plans with functions

[ https://issues.apache.org/jira/browse/PHOENIX-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321839#comment-17321839 ] Lars Hofhansl commented on PHOENIX-6445: Two. This should be an invalid query. {code} > explain

[jira] [Commented] (PHOENIX-6445) Wrong query plans with functions

[ https://issues.apache.org/jira/browse/PHOENIX-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321838#comment-17321838 ] Lars Hofhansl commented on PHOENIX-6445: Example one. The group by is missing. {code} >

[jira] [Comment Edited] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321836#comment-17321836 ] Lars Hofhansl edited comment on PHOENIX-6434 at 4/15/21, 1:33 AM: --

[jira] [Comment Edited] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321836#comment-17321836 ] Lars Hofhansl edited comment on PHOENIX-6434 at 4/15/21, 1:33 AM: --

[jira] [Commented] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321836#comment-17321836 ] Lars Hofhansl commented on PHOENIX-6434: Thanks [~kadir] More problems: {code:java} > select

[jira] [Commented] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319684#comment-17319684 ] Lars Hofhansl commented on PHOENIX-6434: So before we can use PHOENIX_ROW_TIMESTAMP for timed

[jira] [Commented] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319683#comment-17319683 ] Lars Hofhansl commented on PHOENIX-6434: And even worse (again with or without this):

[jira] [Commented] (PHOENIX-6434) Secondary Indexes on PHOENIX_ROW_TIMESTAMP()

[ https://issues.apache.org/jira/browse/PHOENIX-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319680#comment-17319680 ] Lars Hofhansl commented on PHOENIX-6434: Tried it and works. There's a funny thing I noticed

[jira] [Commented] (PHOENIX-6436) OrderedResultIterator does bad size estimation

[ https://issues.apache.org/jira/browse/PHOENIX-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314633#comment-17314633 ] Lars Hofhansl commented on PHOENIX-6436: Actually. Even when spooling is disabled, there is

[jira] [Commented] (PHOENIX-6436) OrderedResultIterator does bad size estimation

[ https://issues.apache.org/jira/browse/PHOENIX-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314632#comment-17314632 ] Lars Hofhansl commented on PHOENIX-6436: Yet another option is to limit the maximum amount of

[jira] [Commented] (PHOENIX-6436) OrderedResultIterator does bad size estimation

[ https://issues.apache.org/jira/browse/PHOENIX-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314125#comment-17314125 ] Lars Hofhansl commented on PHOENIX-6436: When spooling is enabled (default) the estimated

  1   2   3   4   5   6   7   8   9   10   >