[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync after changes for global consistent indexes

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17182130#comment-17182130 ] Lars Hofhansl commented on PHOENIX-6090: I think the problem is that * global indexes should

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync after changes for global consistent indexes

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17182101#comment-17182101 ] Lars Hofhansl commented on PHOENIX-6090: If I remove the unlock/relock of the row locks (which

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync after changes for global consistent indexes

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17182057#comment-17182057 ] Lars Hofhansl commented on PHOENIX-6090: Yeah... Just saw that part in the old code. My bad

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync after changes for global consistent indexes

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17182025#comment-17182025 ] Lars Hofhansl commented on PHOENIX-6090: In fact I do not think that is the issue. The new code

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync after changes for global consistent indexes

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181977#comment-17181977 ] Lars Hofhansl commented on PHOENIX-6090: [~kozdemir] that might indeed be the case. Note that

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181628#comment-17181628 ] Lars Hofhansl commented on PHOENIX-6090: Better test, just presplit the table. Shows that

[jira] [Comment Edited] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181528#comment-17181528 ] Lars Hofhansl edited comment on PHOENIX-6090 at 8/21/20, 2:17 AM: --

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181528#comment-17181528 ] Lars Hofhansl commented on PHOENIX-6090: Here's a test that reliably reproduces this.

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181507#comment-17181507 ] Lars Hofhansl commented on PHOENIX-6090: Another area to look is concurrent writes from two

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181390#comment-17181390 ] Lars Hofhansl commented on PHOENIX-6090: [~kozdemir] and I chatted, and it looks like a very

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181344#comment-17181344 ] Lars Hofhansl commented on PHOENIX-6090: I have not seen this happening with a global index. >

[jira] [Comment Edited] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181344#comment-17181344 ] Lars Hofhansl edited comment on PHOENIX-6090 at 8/20/20, 5:17 PM: -- I

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181294#comment-17181294 ] Lars Hofhansl commented on PHOENIX-6090: I used the indexUpgradeTool to "rollback" this table,

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181050#comment-17181050 ] Lars Hofhansl commented on PHOENIX-6090: [~kozdemir] missed your comment between all my

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181047#comment-17181047 ] Lars Hofhansl commented on PHOENIX-6090: I think furthermore this only happens when the *same*

[jira] [Comment Edited] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181023#comment-17181023 ] Lars Hofhansl edited comment on PHOENIX-6090 at 8/20/20, 8:29 AM: -- And

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181023#comment-17181023 ] Lars Hofhansl commented on PHOENIX-6090: And at least the regionserver died with this:

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181010#comment-17181010 ] Lars Hofhansl commented on PHOENIX-6090: One more thing. This *only* happens with overwrites

[jira] [Comment Edited] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180995#comment-17180995 ] Lars Hofhansl edited comment on PHOENIX-6090 at 8/20/20, 7:40 AM: -- To

[jira] [Comment Edited] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180995#comment-17180995 ] Lars Hofhansl edited comment on PHOENIX-6090 at 8/20/20, 7:40 AM: -- To

[jira] [Comment Edited] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180995#comment-17180995 ] Lars Hofhansl edited comment on PHOENIX-6090 at 8/20/20, 7:22 AM: -- To

[jira] [Commented] (PHOENIX-6090) Local indexes get out of sync in 5.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180995#comment-17180995 ] Lars Hofhansl commented on PHOENIX-6090: To reproduce: {code:java} -- In sqlline: > create

[jira] [Commented] (PHOENIX-6089) Additional relocations for the 5.1.0 client

[ https://issues.apache.org/jira/browse/PHOENIX-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180968#comment-17180968 ] Lars Hofhansl commented on PHOENIX-6089: Please have a look. If there's an easier way to this,

[jira] [Commented] (PHOENIX-6088) Local indexes are not updated in 5.1.x

[ https://issues.apache.org/jira/browse/PHOENIX-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180947#comment-17180947 ] Lars Hofhansl commented on PHOENIX-6088: OK... It had to do with the HBase versions... But it

[jira] [Comment Edited] (PHOENIX-6088) Local indexes are not updated in 5.1.x

[ https://issues.apache.org/jira/browse/PHOENIX-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180896#comment-17180896 ] Lars Hofhansl edited comment on PHOENIX-6088 at 8/20/20, 1:02 AM: -- Not

[jira] [Commented] (PHOENIX-6088) Local indexes are not updated in 5.1.x

[ https://issues.apache.org/jira/browse/PHOENIX-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180896#comment-17180896 ] Lars Hofhansl commented on PHOENIX-6088: Not sure how this got through tests. (Or maybe it

[jira] [Commented] (PHOENIX-4286) Create EXPORT SCHEMA command

[ https://issues.apache.org/jira/browse/PHOENIX-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17175842#comment-17175842 ] Lars Hofhansl commented on PHOENIX-4286: What would the syntax look like? Other databases have

[jira] [Commented] (PHOENIX-6066) MetaDataEndpointImpl.doGetTable should acquire a readLock instead of an exclusive writeLock on the table header row

[ https://issues.apache.org/jira/browse/PHOENIX-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17175134#comment-17175134 ] Lars Hofhansl commented on PHOENIX-6066: Good find. Logically it should not be needed. (I do

[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=17175130#comment-17175130 ] Lars Hofhansl commented on PHOENIX-6064: Hmm... Isn't that a cop-out? It just means that Tephra

[jira] [Commented] (PHOENIX-6057) Create phoenix-connector for spark, kafka, pig, flume that works with Phoenix5

[ https://issues.apache.org/jira/browse/PHOENIX-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172753#comment-17172753 ] Lars Hofhansl commented on PHOENIX-6057: What about the Presto connector (in Presto)? It

[jira] [Commented] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169388#comment-17169388 ] Lars Hofhansl commented on PHOENIX-6045: Not a big deal, but I noticed that this was committed

[jira] [Comment Edited] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165959#comment-17165959 ] Lars Hofhansl edited comment on PHOENIX-6045 at 7/27/20, 9:20 PM: --

[jira] [Comment Edited] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165959#comment-17165959 ] Lars Hofhansl edited comment on PHOENIX-6045 at 7/27/20, 9:06 PM: --

[jira] [Comment Edited] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165959#comment-17165959 ] Lars Hofhansl edited comment on PHOENIX-6045 at 7/27/20, 8:57 PM: --

[jira] [Commented] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165959#comment-17165959 ] Lars Hofhansl commented on PHOENIX-6045: Sorry for my verbose thought process here. But

[jira] [Commented] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165471#comment-17165471 ] Lars Hofhansl commented on PHOENIX-6045: Yeah, the comment is misguided or incomplete. The

[jira] [Comment Edited] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165138#comment-17165138 ] Lars Hofhansl edited comment on PHOENIX-6045 at 7/27/20, 6:29 AM: -- I

[jira] [Commented] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165138#comment-17165138 ] Lars Hofhansl commented on PHOENIX-6045: I think that would never work. If you don't find the

[jira] [Comment Edited] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164759#comment-17164759 ] Lars Hofhansl edited comment on PHOENIX-6045 at 7/25/20, 6:04 AM: --

[jira] [Commented] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164759#comment-17164759 ] Lars Hofhansl commented on PHOENIX-6045: It's not using any index because neither index covers

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158804#comment-17158804 ] Lars Hofhansl commented on PHOENIX-6000: [~kozdemir] pointed out that I added mutable parameter

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158698#comment-17158698 ] Lars Hofhansl commented on PHOENIX-6000: Right name this time, and fixed the test after

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158676#comment-17158676 ] Lars Hofhansl commented on PHOENIX-6000: Oh. Lemme change the name of the patch. (old habits).

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158506#comment-17158506 ] Lars Hofhansl commented on PHOENIX-6000: [~gjacoby], any thoughts? > Client side DELETEs

[jira] [Comment Edited] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157037#comment-17157037 ] Lars Hofhansl edited comment on PHOENIX-6000 at 7/13/20, 11:46 PM: ---

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157037#comment-17157037 ] Lars Hofhansl commented on PHOENIX-6000: -v2 contains a set. Sets up two indexes (one global

[jira] [Comment Edited] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157037#comment-17157037 ] Lars Hofhansl edited comment on PHOENIX-6000 at 7/13/20, 11:42 PM: ---

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155841#comment-17155841 ] Lars Hofhansl commented on PHOENIX-6000: Actually I cannot find a test for this scenario at

[jira] [Commented] (PHOENIX-5990) Delete statements don't honor index hints

[ https://issues.apache.org/jira/browse/PHOENIX-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155765#comment-17155765 ] Lars Hofhansl commented on PHOENIX-5990: [~dbwong] that comment seems incorrect. I saw that

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155760#comment-17155760 ] Lars Hofhansl commented on PHOENIX-6000: [~gjacoby] I just moved the boolean check up. See the

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155651#comment-17155651 ] Lars Hofhansl commented on PHOENIX-6000: Here's the breathtakingly complex patch. Maybe let's

[jira] [Commented] (PHOENIX-6000) Client side DELETEs should use local indexes for filtering

[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155649#comment-17155649 ] Lars Hofhansl commented on PHOENIX-6000: [~kozdemir], [~gjacoby], [~abhishek.chouhan],

[jira] [Commented] (PHOENIX-5953) Set CurrentSCN value can not write data

[ https://issues.apache.org/jira/browse/PHOENIX-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134975#comment-17134975 ] Lars Hofhansl commented on PHOENIX-5953: Writing as of an SCN would be rewriting history. If

[jira] [Commented] (PHOENIX-5902) Document or fix new compat jar behavior.

[ https://issues.apache.org/jira/browse/PHOENIX-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132691#comment-17132691 ] Lars Hofhansl commented on PHOENIX-5902: For now this patch is good. +1 (It's never good to

[jira] [Commented] (PHOENIX-5902) Document or fix new compat jar behavior.

[ https://issues.apache.org/jira/browse/PHOENIX-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132688#comment-17132688 ] Lars Hofhansl commented on PHOENIX-5902: [~apurtell] what we discussed earlier this week. I

[jira] [Commented] (PHOENIX-5903) Mark more hbase dependency's scope as provided for phoenix-server

[ https://issues.apache.org/jira/browse/PHOENIX-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132686#comment-17132686 ] Lars Hofhansl commented on PHOENIX-5903: What about Phoenix 4.x? > Mark more hbase

[jira] [Commented] (PHOENIX-5902) Document or fix new compat jar behavior.

[ https://issues.apache.org/jira/browse/PHOENIX-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125519#comment-17125519 ] Lars Hofhansl commented on PHOENIX-5902: > [would] not [work] for the thick client jar Good

[jira] [Comment Edited] (PHOENIX-5902) Document or fix new compat jar behavior.

[ https://issues.apache.org/jira/browse/PHOENIX-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125122#comment-17125122 ] Lars Hofhansl edited comment on PHOENIX-5902 at 6/3/20, 4:43 PM: -

[jira] [Commented] (PHOENIX-5902) Document or fix new compat jar behavior.

[ https://issues.apache.org/jira/browse/PHOENIX-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125122#comment-17125122 ] Lars Hofhansl commented on PHOENIX-5902: Actually I think it's nicer to keep the compat jar out

[jira] [Commented] (PHOENIX-5902) Document or fix new compat jar behavior.

[ https://issues.apache.org/jira/browse/PHOENIX-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125120#comment-17125120 ] Lars Hofhansl commented on PHOENIX-5902: Sorry. Have been quite busy... Looking now. (And for

[jira] [Commented] (PHOENIX-5656) Make Phoenix scripts work with Python 3

[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109702#comment-17109702 ] Lars Hofhansl commented on PHOENIX-5656: {\{x.decode().partition('=')}} ? > Make Phoenix

[jira] [Commented] (PHOENIX-5404) Move check to client side to see if there are any child views that need to be dropped while receating a table/view

[ https://issues.apache.org/jira/browse/PHOENIX-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109648#comment-17109648 ] Lars Hofhansl commented on PHOENIX-5404: I agree. I think we should clean up these things now

[jira] [Comment Edited] (PHOENIX-5656) Make Phoenix scripts work with Python 3

[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101024#comment-17101024 ] Lars Hofhansl edited comment on PHOENIX-5656 at 5/6/20, 5:18 PM: -

[jira] [Commented] (PHOENIX-5656) Make Phoenix scripts work with Python 3

[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101024#comment-17101024 ] Lars Hofhansl commented on PHOENIX-5656: [~RichardAntal] Thanks for picking this up. I've been

[jira] [Commented] (PHOENIX-5812) Automatically Close "Idle" Long Open Connections

[ https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080619#comment-17080619 ] Lars Hofhansl commented on PHOENIX-5812: What about [~pawan.prakash]'s comment about not

[jira] [Comment Edited] (PHOENIX-5607) Client-server backward compatibility tests

[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076832#comment-17076832 ] Lars Hofhansl edited comment on PHOENIX-5607 at 4/8/20, 5:59 PM: - Is

[jira] [Commented] (PHOENIX-5607) Client-server backward compatibility tests

[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076832#comment-17076832 ] Lars Hofhansl commented on PHOENIX-5607: Is there a forward part jira for master?

[jira] [Commented] (PHOENIX-5629) Phoenix Function to Return HBase row timestamp

[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048489#comment-17048489 ] Lars Hofhansl commented on PHOENIX-5629: [~tkhurana] I see. Thanks. [~ckulkarni] I'd vote for

[jira] [Commented] (PHOENIX-5629) Phoenix Function to Return HBase row timestamp

[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047984#comment-17047984 ] Lars Hofhansl commented on PHOENIX-5629: Can we change the name? To just "ROW_TIMESTAMP". It's

[jira] [Comment Edited] (PHOENIX-5629) Phoenix Function to Return HBase row timestamp

[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047936#comment-17047936 ] Lars Hofhansl edited comment on PHOENIX-5629 at 2/28/20 9:48 PM: - So

[jira] [Commented] (PHOENIX-5629) Phoenix Function to Return HBase row timestamp

[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047936#comment-17047936 ] Lars Hofhansl commented on PHOENIX-5629: So this returns a data, why is it called

[jira] [Commented] (PHOENIX-5607) Client-server backward compatibility tests

[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042622#comment-17042622 ] Lars Hofhansl commented on PHOENIX-5607: Looks like your test found a backwards compatibility

[jira] [Commented] (PHOENIX-5601) Add a new Coprocessor - ViewTTLAware Coprocessor

[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033091#comment-17033091 ] Lars Hofhansl commented on PHOENIX-5601: For the record. I am not a fan of this. Phoenix has

[jira] [Commented] (PHOENIX-5607) Client-server backward compatibility tests

[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028712#comment-17028712 ] Lars Hofhansl commented on PHOENIX-5607: Hi [~sandeep.guggilam]. Looks good. Does each

[jira] [Commented] (PHOENIX-5677) Replace System.currentTimeMillis with EnvironmentEdgeManager in non-test code

[ https://issues.apache.org/jira/browse/PHOENIX-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021774#comment-17021774 ] Lars Hofhansl commented on PHOENIX-5677: Cool. Missed that. Fine to disable/remove the test.

[jira] [Commented] (PHOENIX-5677) Replace System.currentTimeMillis with EnvironmentEdgeManager in non-test code

[ https://issues.apache.org/jira/browse/PHOENIX-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021750#comment-17021750 ] Lars Hofhansl commented on PHOENIX-5677: That's why we have the test-suite :) Looks like this

[jira] [Commented] (PHOENIX-5629) Phoenix Function to Return HBase Timestamp of Column Cell

[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019892#comment-17019892 ] Lars Hofhansl commented on PHOENIX-5629: They are concatenated only for immutable tables and

[jira] [Commented] (PHOENIX-5672) Unable to find cached index metadata with large UPSERT/SELECT and local index.

[ https://issues.apache.org/jira/browse/PHOENIX-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019738#comment-17019738 ] Lars Hofhansl commented on PHOENIX-5672: I'm going to close this. The timeout just needs to be

[jira] [Commented] (PHOENIX-5672) Unable to find cached index metadata with large UPSERT/SELECT and local index.

[ https://issues.apache.org/jira/browse/PHOENIX-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019739#comment-17019739 ] Lars Hofhansl commented on PHOENIX-5672: PHOENIX-5688 is related... > Unable to find cached

[jira] [Commented] (PHOENIX-5688) Investigate better client/server work pacing

[ https://issues.apache.org/jira/browse/PHOENIX-5688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019726#comment-17019726 ] Lars Hofhansl commented on PHOENIX-5688: In fact it's generally a nice scheme, even for

[jira] [Commented] (PHOENIX-5688) Investigate better client/server work pacing

[ https://issues.apache.org/jira/browse/PHOENIX-5688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019712#comment-17019712 ] Lars Hofhansl commented on PHOENIX-5688: An alternative for #3 is alter the next() method of

[jira] [Commented] (PHOENIX-5688) Investigate better client/server work pacing

[ https://issues.apache.org/jira/browse/PHOENIX-5688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019708#comment-17019708 ] Lars Hofhansl commented on PHOENIX-5688: In case someone is interested in taking this up,

[jira] [Commented] (PHOENIX-5672) Unable to find cached index metadata with large UPSERT/SELECT and local index.

[ https://issues.apache.org/jira/browse/PHOENIX-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018424#comment-17018424 ] Lars Hofhansl commented on PHOENIX-5672: And so another option is to simply increase

[jira] [Commented] (PHOENIX-5686) MetaDataUtil#isLocalIndex returns incorrect results

[ https://issues.apache.org/jira/browse/PHOENIX-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017690#comment-17017690 ] Lars Hofhansl commented on PHOENIX-5686: What's the correct logic? > MetaDataUtil#isLocalIndex

[jira] [Commented] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017632#comment-17017632 ] Lars Hofhansl commented on PHOENIX-5679: I don't think we can just redefine the Phoenix data

[jira] [Commented] (PHOENIX-5672) Unable to find cached index metadata with large UPSERT/SELECT and local index.

[ https://issues.apache.org/jira/browse/PHOENIX-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017560#comment-17017560 ] Lars Hofhansl commented on PHOENIX-5672: Hmm... Correction. The index metadata is currently

[jira] [Comment Edited] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017503#comment-17017503 ] Lars Hofhansl edited comment on PHOENIX-5679 at 1/16/20 9:39 PM: - We

[jira] [Comment Edited] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017503#comment-17017503 ] Lars Hofhansl edited comment on PHOENIX-5679 at 1/16/20 9:38 PM: - We

[jira] [Commented] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017503#comment-17017503 ] Lars Hofhansl commented on PHOENIX-5679: We can fix it with: !set dateFormat "-MM-dd

[jira] [Commented] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017498#comment-17017498 ] Lars Hofhansl commented on PHOENIX-5679: See: 

[jira] [Commented] (PHOENIX-5235) Update SQLline version to the latest

[ https://issues.apache.org/jira/browse/PHOENIX-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017497#comment-17017497 ] Lars Hofhansl commented on PHOENIX-5235: Interestingly this caused the problem outlined in

[jira] [Commented] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017494#comment-17017494 ] Lars Hofhansl commented on PHOENIX-5679: Looks like we're on sqlline 1.5.0, 1.9.0 was just

[jira] [Comment Edited] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017425#comment-17017425 ] Lars Hofhansl edited comment on PHOENIX-5679 at 1/16/20 7:23 PM: - Hence

[jira] [Commented] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017425#comment-17017425 ] Lars Hofhansl commented on PHOENIX-5679: Hence sqlline does the right thing for SQL 92, but now

[jira] [Commented] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017424#comment-17017424 ] Lars Hofhansl commented on PHOENIX-5679: The doc says this: "Please note that this {{DATE}} 

[jira] [Commented] (PHOENIX-5679) Querying a DATE column with 'YYYY-MM-DD HH:MM:SS' format not returning the right data

[ https://issues.apache.org/jira/browse/PHOENIX-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017417#comment-17017417 ] Lars Hofhansl commented on PHOENIX-5679: Hmm... There's DATA and DATATIME, right? (not sure

[jira] [Commented] (PHOENIX-5656) Make Phoenix scripts work with Python 3

[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015655#comment-17015655 ] Lars Hofhansl commented on PHOENIX-5656: -v4 after PHOENIX-5454 > Make Phoenix scripts work

[jira] [Comment Edited] (PHOENIX-5672) Unable to find cached index metadata with large UPSERT/SELECT and local index.

[ https://issues.apache.org/jira/browse/PHOENIX-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015368#comment-17015368 ] Lars Hofhansl edited comment on PHOENIX-5672 at 1/14/20 11:17 PM: --

[jira] [Comment Edited] (PHOENIX-5645) BaseScannerRegionObserver should prevent compaction from purging very recently deleted cells

[ https://issues.apache.org/jira/browse/PHOENIX-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015474#comment-17015474 ] Lars Hofhansl edited comment on PHOENIX-5645 at 1/14/20 11:11 PM: --

[jira] [Commented] (PHOENIX-5645) BaseScannerRegionObserver should prevent compaction from purging very recently deleted cells

[ https://issues.apache.org/jira/browse/PHOENIX-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015474#comment-17015474 ] Lars Hofhansl commented on PHOENIX-5645: This is breaking MaxLookbackIT. It went unnoticed

<    1   2   3   4   5   6   7   8   9   10   >