[
https://issues.apache.org/jira/browse/PHOENIX-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-6129:
--
Summary: Optimize tableExists() call while retrieving correct MUTEX table
(was: Remove unnec
[
https://issues.apache.org/jira/browse/PHOENIX-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-6203:
--
Fix Version/s: 4.16.0
5.1.0
> CQS.getTable(byte[] tableName) does not thro
[
https://issues.apache.org/jira/browse/PHOENIX-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned PHOENIX-6203:
-
Assignee: Viraj Jasani
> CQS.getTable(byte[] tableName) does not throw TNFE even if ta
Viraj Jasani created PHOENIX-6203:
-
Summary: CQS.getTable(byte[] tableName) does not throw TNFE even
if table doesn't exist
Key: PHOENIX-6203
URL: https://issues.apache.org/jira/browse/PHOENIX-6203
Pr
[
https://issues.apache.org/jira/browse/PHOENIX-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam updated PHOENIX-6202:
Description:
{code:java}
@Test
public void testGlobalAddColumns() throws Exception {
[
https://issues.apache.org/jira/browse/PHOENIX-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam updated PHOENIX-6202:
Description:
{code:java}
@Test
public void testGlobalAddColumns() throws Exception {
[
https://issues.apache.org/jira/browse/PHOENIX-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam updated PHOENIX-6202:
Description:
{code:java}
@Test
public void testGlobalAddColumns() throws Exception {
Swaroopa Kadam created PHOENIX-6202:
---
Summary: New column in index gets added as PK with CASCADE INDEX
Key: PHOENIX-6202
URL: https://issues.apache.org/jira/browse/PHOENIX-6202
Project: Phoenix
Istvan Toth created PHOENIX-6201:
Summary: Add Release Notes field to Phoenix JIRA projects
Key: PHOENIX-6201
URL: https://issues.apache.org/jira/browse/PHOENIX-6201
Project: Phoenix
Issue Ty
Thank you Ankit, Rajeshbabu, and Josh!
RELEASNOTES.md and CHANGES.md are automatically populated from Jira by the
hbase-derived release script currently under review.
I am noticing that our tickets do not have a Release Notes field.
I'll add the field in JIRA for the Phoenix projects (if I can fi
Thanks for your feedback Geoffrey and Josh.
I've opened
https://issues.apache.org/jira/browse/INFRA-21015
for the SVN space.
On Wed, Oct 21, 2020 at 6:39 PM Josh Elser wrote:
> Sounds good to me. Yes, would say that private SVN space is good.
>
> I can't find any existing private space, so I t
[
https://issues.apache.org/jira/browse/PHOENIX-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana updated PHOENIX-6200:
---
Summary: Add counters for extra index rows, log results to PIT and
PIT_RESULT table (was:
Tanuj Khurana created PHOENIX-6200:
--
Summary: Add counters for extra index rows, log results to PIT and
PIT_RESULT
Key: PHOENIX-6200
URL: https://issues.apache.org/jira/browse/PHOENIX-6200
Project: P
[
https://issues.apache.org/jira/browse/PHOENIX-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana reassigned PHOENIX-6200:
--
Assignee: Tanuj Khurana
> Add counters for extra index rows, log results to PIT and
Sounds good to me. Yes, would say that private SVN space is good.
I can't find any existing private space, so I think it would be an ask
to infra, e.g. https://issues.apache.org/jira/browse/INFRA-15461
On 10/21/20 1:23 AM, Istvan Toth wrote:
Hi!
I've recently implemented the Yetus PR checks
[
https://issues.apache.org/jira/browse/PHOENIX-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana reassigned PHOENIX-6199:
--
Assignee: Tanuj Khurana
> Generate different query plan depending upon if the source
[
https://issues.apache.org/jira/browse/PHOENIX-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana reassigned PHOENIX-6198:
--
Assignee: Tanuj Khurana
> Add option to IndexTool to specify the source table for sc
Tanuj Khurana created PHOENIX-6199:
--
Summary: Generate different query plan depending upon if the
source is index table or data table
Key: PHOENIX-6199
URL: https://issues.apache.org/jira/browse/PHOENIX-6199
Tanuj Khurana created PHOENIX-6198:
--
Summary: Add option to IndexTool to specify the source table for
scan
Key: PHOENIX-6198
URL: https://issues.apache.org/jira/browse/PHOENIX-6198
Project: Phoenix
Not sure about the credential storage, but yes, using a bot account makes a
lot of sense.
Geoffrey
On Wed, Oct 21, 2020 at 12:24 AM Istvan Toth wrote:
> Hi!
>
> I've recently implemented the Yetus PR checks for GitHub PR, which for the
> most part seem to work well.
>
> However, it seems that n
+1 (binding)
* L&N seem fine
* RELEASENOTES.md is empty, maybe we'll have content in there later?
(Mentioning in case there should have been content)
* phoenix-shaded-guava jar looks sane
* apache-rat:check passes
* Nice content in CHANGES.md
* Built phoenix.git with this release
On 10/14/20 3
+1(binding)
verified the release - ok
Thanks,
Rajeshbabu.
On Wed, Oct 21, 2020 at 6:14 AM Ankit Singhal
wrote:
> +1(binding)
>
> * License and Notice - OK
> * Build from the source - OK
> * Used the above-created artifact 1.0.0 and build the Phoenix master - OK
> * Signature/checksums - Ok
> *
22 matches
Mail list logo
