Re: Incorrect number of rows affected from DELETE query

Phoenix returns the number of delete markers that were placed if it’s a point delete, not the actual number of rows deleted. Otherwise you’d need to do a read before the delete (which would be costly). It’s possible that this could be made configurable - please file a JIRA. You could work around th

Phoenix admin?

Hi team, I created a table through HBase api, and then created a view for it on Phoenix. And for some reasons, i dropped the view, but coprocessors are still attached on this table. >From hbase webui: 'recommend:vulgar_feed', {TABLE_ATTRIBUTES => {coprocessor$1 => '|org.apache.phoenix.coprocess

Re: Incorrect number of rows affected from DELETE query

Hi Jins, If you provide steps to reproduce it would be much easier to understand where the problem is. If nothing was deleted the report should be 'No rows affected'. Thanks, Sergey On Mon, Feb 19, 2018 at 4:30 PM, Jins George wrote: > Hi, > > I am facing an issue in which the number of rows af

Error Occurs while selecting a specific set of columns

Hi, https://issues.apache.org/jira/browse/PHOENIX-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel Is there any work around/fix for this issue? Thanks and regards, Akshay

Re: Runtime DDL supported?

Another option would be to use dynamic columns[1] when querying across views. You’d have to disable column encoding [2] in this case. [1] http://phoenix.apache.org/dynamic_columns.html [2] http://phoenix.apache.org/columnencoding.html On Wed, Feb 21, 2018 at 11:57 PM Miles Spielberg wrote: > I

Spark Phoenix index usage

Good mooning at all, thank you for your wonderful work. Apache Phoenix really saves me in the past. I have one question, If I use Spark for connection to Phoenix, I have 2 ways: 1. JDBC 2. Apache Spark Plugin I would like to use spark for read