Re: Phoenix-Spark driver structured streaming support?

Thanks, but this is just a sample test i was doing. My use case is to read data from Kafka in a streaming fashion and then write to Phoenix. On Thu, Feb 22, 2018 at 5:15 PM, Pedro Boado wrote: > No it's not supported. > > Why don't you just run your example in spark

[jira] [Commented] (PHOENIX-4530) Do not collect delete markers during major compaction of table with disabled mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373844#comment-16373844 ] Hudson commented on PHOENIX-4530: - FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1821

[jira] [Commented] (PHOENIX-4530) Do not collect delete markers during major compaction of table with disabled mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373814#comment-16373814 ] Hudson commented on PHOENIX-4530: - FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #47 (See

[jira] [Commented] (PHOENIX-4530) Do not collect delete markers during major compaction of table with disabled mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373790#comment-16373790 ] Vincent Poon commented on PHOENIX-4530: --- Committed to 4.x and master branches. Still working on a

[jira] [Updated] (PHOENIX-4530) Do not collect delete markers during major compaction of table with disabled mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4530: -- Affects Version/s: 4.13.0 Fix Version/s: 4.14.0 > Do not collect delete markers

[jira] [Updated] (PHOENIX-4530) Do not collect delete markers during major compaction of table with disabled mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4530: -- Attachment: PHOENIX-4530.4.x-HBase-1.1.v2.patch

Re: Phoenix-Spark driver structured streaming support?

No it's not supported. Why don't you just run your example in spark batch and save the dataframe/rdd to Phoenix? Your data is coming from a json file (which at the end is a static source, not a stream) On 23 Feb 2018 01:08, "Suhas H M" wrote: > Hi, > > Is spark

Phoenix-Spark driver structured streaming support?

Hi, Is spark structured streaming supported using Phoenix-Spark driver? when phoenix-spark driver is used to write the structured streamed data, we get the exception Exception in thread "main" java.lang.UnsupportedOperationException: Data source org.apache.phoenix.spark does not support

[jira] [Commented] (PHOENIX-4607) Allow PhoenixInputFormat to use tenant-specific connections

[ https://issues.apache.org/jira/browse/PHOENIX-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373751#comment-16373751 ] Geoffrey Jacoby commented on PHOENIX-4607: -- The test failures go away when run against HBase

[jira] [Created] (PHOENIX-4627) Phoenix-Spark doesn't supported spark structured streaming

Suhas created PHOENIX-4627: -- Summary: Phoenix-Spark doesn't supported spark structured streaming Key: PHOENIX-4627 URL: https://issues.apache.org/jira/browse/PHOENIX-4627 Project: Phoenix Issue

[jira] [Created] (PHOENIX-4626) Increase time allowed for partial index rebuild to complete

James Taylor created PHOENIX-4626: - Summary: Increase time allowed for partial index rebuild to complete Key: PHOENIX-4626 URL: https://issues.apache.org/jira/browse/PHOENIX-4626 Project: Phoenix

[jira] [Commented] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373707#comment-16373707 ] James Taylor commented on PHOENIX-4148: --- I'll go ahead and commit your patch unless I hear

[jira] [Commented] (PHOENIX-4607) Allow PhoenixInputFormat to use tenant-specific connections

[ https://issues.apache.org/jira/browse/PHOENIX-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373636#comment-16373636 ] James Taylor commented on PHOENIX-4607: --- Phoenix on master uses HBase 1.4 which has known test

[jira] [Commented] (PHOENIX-4607) Allow PhoenixInputFormat to use tenant-specific connections

[ https://issues.apache.org/jira/browse/PHOENIX-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373630#comment-16373630 ] Geoffrey Jacoby commented on PHOENIX-4607: -- HadoopQA doesn't seem to be posting to the JIRA,

[jira] [Commented] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373502#comment-16373502 ] Hudson commented on PHOENIX-4625: - SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #46 (See

[jira] [Commented] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373407#comment-16373407 ] Hudson commented on PHOENIX-4625: - SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1820

[jira] [Updated] (PHOENIX-4548) UpgradeUtil.mapChildViewsToNamespace does not handle multi-tenant views that have the same name.

[ https://issues.apache.org/jira/browse/PHOENIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4548: Fix Version/s: 5.0.0 > UpgradeUtil.mapChildViewsToNamespace does not handle multi-tenant

[jira] [Commented] (PHOENIX-4548) UpgradeUtil.mapChildViewsToNamespace does not handle multi-tenant views that have the same name.

[ https://issues.apache.org/jira/browse/PHOENIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373228#comment-16373228 ] Thomas D'Silva commented on PHOENIX-4548: - [~rajeshbabu] Sorry for the delayed response, looks

[jira] [Commented] (PHOENIX-4530) Do not collect delete markers during major compaction of table with disabled mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373225#comment-16373225 ] James Taylor commented on PHOENIX-4530: --- Thanks for confirming, [~vincentpoon]. Please commit to

[jira] [Commented] (PHOENIX-4333) Incorrect estimate when stats are updated on a tenant specific view

[ https://issues.apache.org/jira/browse/PHOENIX-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373223#comment-16373223 ] James Taylor commented on PHOENIX-4333: --- Please review, [~tdsilva]. If you have spare cycles to

[jira] [Updated] (PHOENIX-4333) Incorrect estimate when stats are updated on a tenant specific view

[ https://issues.apache.org/jira/browse/PHOENIX-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4333: -- Attachment: PHOENIX-4333_v3.patch > Incorrect estimate when stats are updated on a tenant

[jira] [Commented] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373201#comment-16373201 ] Thomas D'Silva commented on PHOENIX-4625: - Sure I will get this committed today. > memory leak

[jira] [Assigned] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva reassigned PHOENIX-4625: --- Assignee: Vikas Vishwakarma > memory leak in PhoenixConnection if scanner renew

[jira] [Commented] (PHOENIX-4609) Error Occurs while selecting a specific set of columns : ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 2

[ https://issues.apache.org/jira/browse/PHOENIX-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373199#comment-16373199 ] Aman Jha commented on PHOENIX-4609: --- [~elserj] are you sure? the stack trace seems different for both

[jira] [Commented] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373188#comment-16373188 ] James Taylor commented on PHOENIX-4625: --- [~tdsilva] - would you have some spare cycles to commit

[jira] [Commented] (PHOENIX-4609) Error Occurs while selecting a specific set of columns : ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 2

[ https://issues.apache.org/jira/browse/PHOENIX-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373131#comment-16373131 ] Josh Elser commented on PHOENIX-4609: - You may be running into PHOENIX-4588 > Error Occurs while