[jira] [Created] (PHOENIX-3844) "Unsupported literal value" when using ANY with a nested query selecting an array

Danny Dvinov created PHOENIX-3844: - Summary: "Unsupported literal value" when using ANY with a nested query selecting an array Key: PHOENIX-3844 URL: https://issues.apache.org/jira/browse/PHOENIX-3844

[jira] [Commented] (PHOENIX-3834) Provide a way to collect stats and not use it for query parallelization

[ https://issues.apache.org/jira/browse/PHOENIX-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004058#comment-16004058 ] Samarth Jain commented on PHOENIX-3834: --- With the help of this config, we could also possibly

[jira] [Commented] (PHOENIX-3758) PhoenixMetricsIT#testGlobalPhoenixMetricsForQueries fails intermittently

[ https://issues.apache.org/jira/browse/PHOENIX-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004030#comment-16004030 ] Sneha Kanekar commented on PHOENIX-3758: Any update on this? >

[jira] [Commented] (PHOENIX-3769) OnDuplicateKeyIT#testNewAndMultiDifferentUpdateOnSingleColumn fails on ppc64le

[ https://issues.apache.org/jira/browse/PHOENIX-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004028#comment-16004028 ] Sneha Kanekar commented on PHOENIX-3769: Any update on this issue? >

[jira] [Commented] (PHOENIX-3811) Do not disable index on write failure by default

[ https://issues.apache.org/jira/browse/PHOENIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003977#comment-16003977 ] Hadoop QA commented on PHOENIX-3811: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3811) Do not disable index on write failure by default

[ https://issues.apache.org/jira/browse/PHOENIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3811: -- Attachment: PHOENIX-3811_v1.patch > Do not disable index on write failure by default >

[jira] [Updated] (PHOENIX-3811) Do not disable index on write failure by default

[ https://issues.apache.org/jira/browse/PHOENIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3811: -- Summary: Do not disable index on write failure by default (was: Do not disable index on

[jira] [Commented] (PHOENIX-3842) Turn off all BloomFilter for Phoenix tables

[ https://issues.apache.org/jira/browse/PHOENIX-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003883#comment-16003883 ] James Taylor commented on PHOENIX-3842: --- +1 > Turn off all BloomFilter for Phoenix tables >

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003881#comment-16003881 ] Lars Hofhansl commented on PHOENIX-3797: Filed PHOENIX-3842 and posted a patch there. *This* is

[jira] [Updated] (PHOENIX-3842) Turn off all BloomFilter for Phoenix tables

[ https://issues.apache.org/jira/browse/PHOENIX-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3842: --- Description: Noticed in PHOENIX-3797. Exception with BFs, when there shouldn't have been

[jira] [Commented] (PHOENIX-3842) Turn off all BloomFilter for Phoenix tables

[ https://issues.apache.org/jira/browse/PHOENIX-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003872#comment-16003872 ] Lars Hofhansl commented on PHOENIX-3842: [~jamestaylor], [~apurtell], FYI. > Turn off all

[jira] [Assigned] (PHOENIX-3842) Turn off all BloomFilter for Phoenix tables

[ https://issues.apache.org/jira/browse/PHOENIX-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-3842: -- Assignee: Lars Hofhansl > Turn off all BloomFilter for Phoenix tables >

[jira] [Updated] (PHOENIX-3842) Turn off all BloomFilter for Phoenix tables

[ https://issues.apache.org/jira/browse/PHOENIX-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3842: --- Attachment: 3842-4.x-0.98.txt Simple patch with tests. > Turn off all BloomFilter for

[jira] [Created] (PHOENIX-3842) Turn off all BloomFilter for Phoenix tables

Lars Hofhansl created PHOENIX-3842: -- Summary: Turn off all BloomFilter for Phoenix tables Key: PHOENIX-3842 URL: https://issues.apache.org/jira/browse/PHOENIX-3842 Project: Phoenix Issue

[jira] [Commented] (PHOENIX-3832) Local Index - Empty resultset for multi-tenant tables

[ https://issues.apache.org/jira/browse/PHOENIX-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003808#comment-16003808 ] Mujtaba Chohan commented on PHOENIX-3832: - [~lhofhansl] This only happens for multi-tenant

[jira] [Commented] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

[ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003801#comment-16003801 ] James Taylor commented on PHOENIX-3825: --- IMHO, we should write an index row for each version,

[jira] [Commented] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003795#comment-16003795 ] James Taylor commented on PHOENIX-3841: --- +1 on the patch. Thanks for the fix,

[jira] [Commented] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

[ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003772#comment-16003772 ] Vincent Poon commented on PHOENIX-3825: --- Actually, looking at TestIndexUpdateManager, looks like

[jira] [Commented] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003731#comment-16003731 ] Hadoop QA commented on PHOENIX-3841: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003695#comment-16003695 ] Lars Hofhansl commented on PHOENIX-3797: Agree on the blocker prio. The region split under load

[jira] [Updated] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-3841: --- Attachment: PHOENIX-3841.v3.patch > Phoenix View creation failure with Primary

[jira] [Commented] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003685#comment-16003685 ] Maddineni Sukumar commented on PHOENIX-3841: Yes it fixed the issue I was facing because it

[jira] [Comment Edited] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003667#comment-16003667 ] James Taylor edited comment on PHOENIX-3841 at 5/9/17 10:29 PM: Patch

[jira] [Commented] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003667#comment-16003667 ] James Taylor commented on PHOENIX-3841: --- Patch looks good, [~sukuna...@gmail.com]. Would you mind

[jira] [Updated] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-3841: --- Fix Version/s: (was: 4.10.1) 4.11 > Phoenix View creation

[jira] [Commented] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003656#comment-16003656 ] Maddineni Sukumar commented on PHOENIX-3841: Hmm I am newbee in this area so I would simply

[jira] [Commented] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

[ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003653#comment-16003653 ] Vincent Poon commented on PHOENIX-3825: --- [~jamestaylor] Any idea what this method is for?

[jira] [Resolved] (PHOENIX-3798) MutableIndexFailureIT fails since PHOENIX-3789

[ https://issues.apache.org/jira/browse/PHOENIX-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved PHOENIX-3798. - Resolution: Duplicate > MutableIndexFailureIT fails since PHOENIX-3789 >

[jira] [Commented] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra

[ https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003310#comment-16003310 ] James Taylor commented on PHOENIX-3734: --- Thanks for the patch, [~ohads]. [~tdsilva] committed

[jira] [Commented] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003131#comment-16003131 ] James Taylor commented on PHOENIX-3841: --- Rather than the change you made (which will have other

[jira] [Commented] (PHOENIX-3839) Prevent large aggregate queries from timing out

[ https://issues.apache.org/jira/browse/PHOENIX-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003070#comment-16003070 ] Mujtaba Chohan commented on PHOENIX-3839: - Sure [~jamestaylor] I'll try 1.3.1 with HBASE-18000

[jira] [Commented] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003036#comment-16003036 ] Hadoop QA commented on PHOENIX-2885: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3811) Do not disable index on write failure

[ https://issues.apache.org/jira/browse/PHOENIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3811: -- Attachment: PHOENIX-3811-wip7.patch > Do not disable index on write failure >

[jira] [Commented] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002907#comment-16002907 ] Hadoop QA commented on PHOENIX-3841: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

[ https://issues.apache.org/jira/browse/PHOENIX-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-3841: --- Attachment: PHOENIX-3841.patch > Phoenix View creation failure with Primary table

[jira] [Created] (PHOENIX-3841) Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table

Maddineni Sukumar created PHOENIX-3841: -- Summary: Phoenix View creation failure with Primary table not found error when we use update_cache_frequency for primary table Key: PHOENIX-3841 URL:

[jira] [Commented] (PHOENIX-3824) Mutable Index partial rebuild should add only one index row per updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002525#comment-16002525 ] Hudson commented on PHOENIX-3824: - FAILURE: Integrated in Jenkins build Phoenix-master #1606 (See

[jira] [Commented] (PHOENIX-3818) Add client setting to disable server side UPSERT SELECT work

[ https://issues.apache.org/jira/browse/PHOENIX-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002526#comment-16002526 ] Hudson commented on PHOENIX-3818: - FAILURE: Integrated in Jenkins build Phoenix-master #1606 (See

[GitHub] phoenix pull request #246: Connect tal to phoenix

GitHub user ohadshacham reopened a pull request: https://github.com/apache/phoenix/pull/246 Connect tal to phoenix You can merge this pull request into a Git repository by running: $ git pull https://github.com/ohadshacham/phoenix ConnectTALtoPhoenix Alternatively you can

[GitHub] phoenix pull request #246: Connect tal to phoenix

Github user ohadshacham closed the pull request at: https://github.com/apache/phoenix/pull/246 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] phoenix pull request #246: Connect tal to phoenix

GitHub user ohadshacham opened a pull request: https://github.com/apache/phoenix/pull/246 Connect tal to phoenix You can merge this pull request into a Git repository by running: $ git pull https://github.com/ohadshacham/phoenix ConnectTALtoPhoenix Alternatively you can

[jira] [Commented] (PHOENIX-3840) Functions extending FirstLastValueBaseFunction returning NAME as null instead of actual function name

[ https://issues.apache.org/jira/browse/PHOENIX-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002371#comment-16002371 ] Loknath Priyatham Teja Singamsetty commented on PHOENIX-3840: -- Fixed the

[jira] [Updated] (PHOENIX-3840) Functions extending FirstLastValueBaseFunction returning NAME as null instead of actual function name

[ https://issues.apache.org/jira/browse/PHOENIX-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Loknath Priyatham Teja Singamsetty updated PHOENIX-3840: - Attachment: PHOENIX-3840.patch > Functions

[jira] [Assigned] (PHOENIX-3840) Functions extending FirstLastValueBaseFunction returning NAME as null instead of actual function name

[ https://issues.apache.org/jira/browse/PHOENIX-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Loknath Priyatham Teja Singamsetty reassigned PHOENIX-3840: Assignee: Loknath Priyatham Teja

[jira] [Created] (PHOENIX-3840) Functions extending FirstLastValueBaseFunction returning NAME as null instead of actual function name

Loknath Priyatham Teja Singamsetty created PHOENIX-3840: Summary: Functions extending FirstLastValueBaseFunction returning NAME as null instead of actual function name Key: PHOENIX-3840

[jira] [Commented] (PHOENIX-3806) Reduce IndexUpdateManager sorting overhead during Index rebuild

[ https://issues.apache.org/jira/browse/PHOENIX-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002235#comment-16002235 ] Hudson commented on PHOENIX-3806: - FAILURE: Integrated in Jenkins build Phoenix-master #1605 (See