[jira] [Created] (PHOENIX-3866) COUNT(col) should scan along required column families only

Lars Hofhansl created PHOENIX-3866: -- Summary: COUNT(col) should scan along required column families only Key: PHOENIX-3866 URL: https://issues.apache.org/jira/browse/PHOENIX-3866 Project: Phoenix

[jira] [Created] (PHOENIX-3865) IS NULL does not return results when STORE_NULLS, and ONE_CELL_PER_COLUMN is set on IMMUTABLE ROWS

Lars Hofhansl created PHOENIX-3865: -- Summary: IS NULL does not return results when STORE_NULLS, and ONE_CELL_PER_COLUMN is set on IMMUTABLE ROWS Key: PHOENIX-3865 URL:

[jira] [Commented] (PHOENIX-3858) Index maintenance not required for local indexes of table with immutable rows

[ https://issues.apache.org/jira/browse/PHOENIX-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015223#comment-16015223 ] Rajeshbabu Chintaguntla commented on PHOENIX-3858: -- [~jamestaylor] Looking into

[jira] [Updated] (PHOENIX-3858) Index maintenance not required for local indexes of table with immutable rows

[ https://issues.apache.org/jira/browse/PHOENIX-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3858: -- Attachment: PHOENIX-3858.patch Here's a WIP patch that prevents the scan to find old values

[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=16014973#comment-16014973 ] Andrew Purtell commented on PHOENIX-3811: - Yes, please, let's keep the default behavior the

[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=16014972#comment-16014972 ] James Taylor commented on PHOENIX-3811: --- We can keep the defaults as they are in the 4.x line and

[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=16014955#comment-16014955 ] Andrew Purtell commented on PHOENIX-3811: - This is not the kind of change that should go into a

[jira] [Updated] (PHOENIX-3864) PhoenixConsumerIT is timing out frequently in 4.x-HBase-0.98

[ https://issues.apache.org/jira/browse/PHOENIX-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3864: -- Attachment: PHOENIX-3864.patch > PhoenixConsumerIT is timing out frequently in 4.x-HBase-0.98

[jira] [Created] (PHOENIX-3864) PhoenixConsumerIT is timing out frequently in 4.x-HBase-0.98

James Taylor created PHOENIX-3864: - Summary: PhoenixConsumerIT is timing out frequently in 4.x-HBase-0.98 Key: PHOENIX-3864 URL: https://issues.apache.org/jira/browse/PHOENIX-3864 Project: Phoenix

[jira] [Commented] (PHOENIX-3209) Ensure scans run at specific server timestamp for UPSERT SELECT to same table

[ https://issues.apache.org/jira/browse/PHOENIX-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014887#comment-16014887 ] James Taylor commented on PHOENIX-3209: --- When a client uses the UPDATE_CACHE_FREQUENCY feature,

[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=16014886#comment-16014886 ] Hudson commented on PHOENIX-3840: - FAILURE: Integrated in Jenkins build Phoenix-master #1614 (See

[jira] [Commented] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014845#comment-16014845 ] James Taylor commented on PHOENIX-3823: --- Thanks for the patch, [~sukuna...@gmail.com]. It's

[jira] [Resolved] (PHOENIX-3861) Add function DAYOFWEEK(date/datetime)

[ https://issues.apache.org/jira/browse/PHOENIX-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3861. --- Resolution: Fixed We already have DAYOFWEEK from PHOENIX-3201 (which returns an INTEGER

[jira] [Commented] (PHOENIX-3863) Document DAYOFWEEK, DAYOFYEAR, and any other missing functions

[ https://issues.apache.org/jira/browse/PHOENIX-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014774#comment-16014774 ] James Taylor commented on PHOENIX-3863: --- If you have a few spare cycles, this would be one we

[jira] [Created] (PHOENIX-3863) Document DAYOFWEEK, DAYOFYEAR, and any other missing functions

James Taylor created PHOENIX-3863: - Summary: Document DAYOFWEEK, DAYOFYEAR, and any other missing functions Key: PHOENIX-3863 URL: https://issues.apache.org/jira/browse/PHOENIX-3863 Project: Phoenix

[jira] [Resolved] (PHOENIX-3859) Upsert Select query returning updated count as double than actual value when total count is more than configured mutate batch size

[ https://issues.apache.org/jira/browse/PHOENIX-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3859. --- Resolution: Fixed This is a known issue and a duplicate of PHOENIX-3178 (not related to

[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=16014653#comment-16014653 ] Samarth Jain commented on PHOENIX-3840: --- Committed to 4.x, 4.10 and master branches. > Functions

[jira] [Resolved] (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 ] Samarth Jain resolved PHOENIX-3840. --- Resolution: Fixed > Functions extending FirstLastValueBaseFunction returning NAME as null

[jira] [Comment Edited] (PHOENIX-3853) Local Index - Writes to local index are twice as slow as global and get exponentially slower with PHOENIX-3827_v2 patch

[ https://issues.apache.org/jira/browse/PHOENIX-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014642#comment-16014642 ] Mujtaba Chohan edited comment on PHOENIX-3853 at 5/17/17 7:15 PM: --

[jira] [Commented] (PHOENIX-3858) Index maintenance not required for local indexes of table with immutable rows

[ https://issues.apache.org/jira/browse/PHOENIX-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014643#comment-16014643 ] Mujtaba Chohan commented on PHOENIX-3858: - Updated PHOENIX-3853 with results for mutable local

[jira] [Comment Edited] (PHOENIX-3858) Index maintenance not required for local indexes of table with immutable rows

[ https://issues.apache.org/jira/browse/PHOENIX-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014643#comment-16014643 ] Mujtaba Chohan edited comment on PHOENIX-3858 at 5/17/17 7:14 PM: --

[jira] [Commented] (PHOENIX-3853) Local Index - Writes to local index are twice as slow as global and get exponentially slower with PHOENIX-3827_v2 patch

[ https://issues.apache.org/jira/browse/PHOENIX-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014642#comment-16014642 ] Mujtaba Chohan commented on PHOENIX-3853: - Performance for *mutable* local index. Again this is

[jira] [Updated] (PHOENIX-3853) Local Index - Writes to local index are twice as slow as global and get exponentially slower with PHOENIX-3827_v2 patch

[ https://issues.apache.org/jira/browse/PHOENIX-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-3853: Attachment: batch_mutable.png > Local Index - Writes to local index are twice as slow as

[jira] [Commented] (PHOENIX-3752) Remove hadoop metrics integration from the tracing framework

[ https://issues.apache.org/jira/browse/PHOENIX-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014640#comment-16014640 ] Samarth Jain commented on PHOENIX-3752: --- Thanks for the updated patch, [~karanmehta93]. Looks good

[jira] [Commented] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

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

[jira] [Commented] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014630#comment-16014630 ] Samarth Jain commented on PHOENIX-3248: --- [~karanmehta93] - sorry for not committing this patch

[jira] [Commented] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

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

[jira] [Updated] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3822: -- Attachment: PHOENIX-3822_v2.patch Thanks for the review, [~jamestaylor]. Please see the

[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=16014557#comment-16014557 ] Samarth Jain commented on PHOENIX-3734: --- Hi, [~ohads]. Make sure to use JRE7 when running phoenix

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014516#comment-16014516 ] Vincent Poon commented on PHOENIX-3807: --- [~elserj] Cool, I'm working on HBASE-18060 which is a

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

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

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014467#comment-16014467 ] Andrew Purtell commented on PHOENIX-3807: - Hey [~elserj], that's great, looking forward to

[jira] [Commented] (PHOENIX-3858) Index maintenance not required for local indexes of table with immutable rows

[ https://issues.apache.org/jira/browse/PHOENIX-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014456#comment-16014456 ] Mujtaba Chohan commented on PHOENIX-3858: - Sure will check it out today. > Index maintenance

[jira] [Updated] (PHOENIX-3862) FastDateFormat does not support the day number of week (1 = Monday, ..., 7 = Sunday) format ('u')

[ https://issues.apache.org/jira/browse/PHOENIX-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Lázaro de Siqueira Júnior updated PHOENIX-3862: Description: The function to_char(date_time, 'u') does

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1601#comment-1601 ] ASF GitHub Bot commented on PHOENIX-3572: - Github user bijugs commented on the issue:

[GitHub] phoenix pull request #229: PHOENIX-3572 Support FETCH NEXT|n ROWS query on c...

Github user bijugs closed the pull request at: https://github.com/apache/phoenix/pull/229 --- 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 is

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014445#comment-16014445 ] ASF GitHub Bot commented on PHOENIX-3572: - Github user bijugs closed the pull request at:

[GitHub] phoenix issue #229: PHOENIX-3572 Support FETCH NEXT|n ROWS query on cursor

Github user bijugs commented on the issue: https://github.com/apache/phoenix/pull/229 Closing the PR since the patch got merged. Thanks @ankitsinghal , @JamesRTaylor . --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[jira] [Created] (PHOENIX-3862) FastDateFormat does not support the day number of week (1 = Monday, ..., 7 = Sunday) format ('u')

José Lázaro de Siqueira Júnior created PHOENIX-3862: --- Summary: FastDateFormat does not support the day number of week (1 = Monday, ..., 7 = Sunday) format ('u') Key: PHOENIX-3862 URL:

[jira] [Commented] (PHOENIX-3209) Ensure scans run at specific server timestamp for UPSERT SELECT to same table

[ https://issues.apache.org/jira/browse/PHOENIX-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014399#comment-16014399 ] Maddineni Sukumar commented on PHOENIX-3209: Hi [~jamestaylor] / [~samarthjain], I am

[jira] [Comment Edited] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014385#comment-16014385 ] Maddineni Sukumar edited comment on PHOENIX-3823 at 5/17/17 4:55 PM: -

[jira] [Updated] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-3823: --- Attachment: PHOENIX-3823.v5.patch New patch with fix for Upsert select scenario

[jira] [Comment Edited] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014382#comment-16014382 ] Rahul Shrivastava edited comment on PHOENIX-3655 at 5/17/17 4:54 PM: -

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014382#comment-16014382 ] Rahul Shrivastava commented on PHOENIX-3655: [~elserj], According to me, the initial design

[jira] [Created] (PHOENIX-3861) Add function DAYOFWEEK(date/datetime)

Lucas Shen created PHOENIX-3861: --- Summary: Add function DAYOFWEEK(date/datetime) Key: PHOENIX-3861 URL: https://issues.apache.org/jira/browse/PHOENIX-3861 Project: Phoenix Issue Type:

[jira] [Commented] (PHOENIX-3788) GLOBAL_MUTATION_BATCH_SIZE should reflect size of chunked batches

[ https://issues.apache.org/jira/browse/PHOENIX-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014333#comment-16014333 ] Geoffrey Jacoby commented on PHOENIX-3788: -- What are the consequences of the client and server

[jira] [Commented] (PHOENIX-3859) Upsert Select query returning updated count as double than actual value when total count is more than configured mutate batch size

[ https://issues.apache.org/jira/browse/PHOENIX-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014315#comment-16014315 ] Geoffrey Jacoby commented on PHOENIX-3859: -- This may be a consequence of PHOENIX-3788. There's

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014297#comment-16014297 ] ASF GitHub Bot commented on PHOENIX-3655: - Github user joshelser commented on a diff in the pull

[GitHub] phoenix pull request #242: PQS metrics - https://issues.apache.org/jira/brow...

Github user joshelser commented on a diff in the pull request: https://github.com/apache/phoenix/pull/242#discussion_r117042628 --- Diff: phoenix-queryserver/src/main/java/org/apache/phoenix/queryserver/metrics/PqsMetricsSystem.java --- @@ -0,0 +1,105 @@ +/* + * Licensed

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014291#comment-16014291 ] ASF GitHub Bot commented on PHOENIX-3655: - Github user joshelser commented on a diff in the pull

[GitHub] phoenix pull request #242: PQS metrics - https://issues.apache.org/jira/brow...

Github user joshelser commented on a diff in the pull request: https://github.com/apache/phoenix/pull/242#discussion_r117041326 --- Diff: phoenix-queryserver/src/main/java/org/apache/phoenix/queryserver/metrics/sink/PqsFileSink.java --- @@ -0,0 +1,66 @@ +/* + * Licensed

[jira] [Assigned] (PHOENIX-3860) Implement TAL functionality for Omid

[ https://issues.apache.org/jira/browse/PHOENIX-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned PHOENIX-3860: - Assignee: Ohad Shacham > Implement TAL functionality for Omid >

[jira] [Created] (PHOENIX-3860) Implement TAL functionality for Omid

Ohad Shacham created PHOENIX-3860: - Summary: Implement TAL functionality for Omid Key: PHOENIX-3860 URL: https://issues.apache.org/jira/browse/PHOENIX-3860 Project: Phoenix Issue Type:

[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=16013980#comment-16013980 ] Ohad Shacham commented on PHOENIX-3734: --- Hi [~giacomotay...@gmail.com] and [~tdsilva], I tried to

[jira] [Commented] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

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

[jira] [Commented] (PHOENIX-3856) StatementContext class constructor not honouring supplied scan object

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

[jira] [Updated] (PHOENIX-3859) Upsert Select query returning updated count as double than actual value when total count is more than configured mutate batch size

[ https://issues.apache.org/jira/browse/PHOENIX-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-3859: --- Priority: Minor (was: Major) > Upsert Select query returning updated count as

[jira] [Updated] (PHOENIX-3859) Upsert Select query returning updated count as double than actual value when total count is more than configured mutate batch size

[ https://issues.apache.org/jira/browse/PHOENIX-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-3859: --- Summary: Upsert Select query returning updated count as double than actual value

[jira] [Created] (PHOENIX-3859) Upsert Select is returning updated count is wrong if overall count is more than configured batch size

Maddineni Sukumar created PHOENIX-3859: -- Summary: Upsert Select is returning updated count is wrong if overall count is more than configured batch size Key: PHOENIX-3859 URL:

[jira] [Updated] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-3823: --- Attachment: PHOENIX-3823.v4.patch > Force cache update on

[jira] [Comment Edited] (PHOENIX-3729) Phoenix 4.7 integration issue with Spark 2.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013662#comment-16013662 ] shekhar reddy edited comment on PHOENIX-3729 at 5/17/17 7:21 AM: - Hello

[jira] [Commented] (PHOENIX-3729) Phoenix 4.7 integration issue with Spark 2.1.0

[ https://issues.apache.org/jira/browse/PHOENIX-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013662#comment-16013662 ] shekhar reddy commented on PHOENIX-3729: Hello Josh Mahonin, I am integrating Phoenix with

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

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

[jira] [Commented] (PHOENIX-3858) Index maintenance not required for local indexes of table with immutable rows

[ https://issues.apache.org/jira/browse/PHOENIX-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013611#comment-16013611 ] James Taylor commented on PHOENIX-3858: --- [~mujtabachohan] can you test with mutable tables for