Skip to main content



HBase Phoenix Cause and Solution for dummy column "_0" or "Column Family:_0"

Cause -
This dummy column is added by Phoenix- if someone created Phoenix table on top of existing HBase table.


Solutions- 

Following solutions can be used to delete _0 column from each row - 
  • Execute Unix command like below - 
echo "scan 'ns:tbl1', {COLUMNS => 'cf:_0'}" |hbase shell | grep "column=cf:_0" | cut -d' ' -f 2 | awk '{$1=$1};1'|sed -e 's/^/delete '"'"'ns:tbl1'"'"', '"'"'/' -e 's/$/'"'"', '"'"'cf:_0'"'"'/'  | hbase shell

Above command will scan rows which has these columns and prepare delete statements and execute them to remove _0 column.

But, above will not give a good performance in case of bigger tables.
-------------------------------------------------------------------------------------------------------------------------
  • Other Solution can be executed from Phoenix Shell 
    • Drop the respective Phoenix table for given HBase table. Refer step below - to drop a Phoenix table without droping HBase Table
    • Recreate the Phoenix table. But, specify "_0" column. For example - 
create table "ns:tbl1"(k VARCHAR primary key, "cf"."name" VARCHAR, "cf"."_0" VARCHAR);
    • Drop the column by executing SQL like below - 
alter table "ns:tbl1" drop column "cf"."_0";
    • If above fails then add column  again to table definition and retry delete. 
alter table "ns:tbl1" add "cf"."_0" VARCHAR;
Note - Failure can be due to Client Timeout or RowTooBigException. Take assistance from admin team to change respective cluster configurations and bounce HBase Master.
    • Once drop column succeeds then drop Phoenix table. Follow below steps, this will drop Phoenix table but will not drop HBase table.
delete from SYSTEM.CATALOG where TABLE_NAME='ns:tbl1';
Note - This will require bounce of Region Server that host regions for table SYSTEM.CATALOG

    • Post that remove Phoenix coo-processors from HBase table by executing below HBase commands
alter 'ns:tbl1' , METHOD => 'table_att_unset',NAME => 'coprocessor$5'

-------------------------------------------------------------------------------------------------------------------------


Comments

Popular posts

Spring MongoDB Rename field with derived Value of another field

Input Collection -  [ { 'k' : 'Troubleshooting' , 'hour' : '2024-10-10T16' , 'v' : [ 'WebPage, Login' ] }, { 'k' : 'TroubleshootingMe' , 'hour' : '2024-10-07T01' , 'v' : [ 'Accounts, etc' ] }  ] Expected Output -  [ { 'hour' : '2024-10-10T16' , 'Troubleshooting' : [ 'WebPage, Login' ] }, { 'hour' : '2024-10-07T01' , 'TroubleshootingMe' : [ 'Accounts, etc' ] }  ]   Above Can be achieved by  $replaceRoot / $replaceWith as follows - { $replaceWith : { $mergeObjects : [ { hour : "$hour" }, { "$arrayToObject" : [ [ { k : "$k" , v : "$v" } ] ] } ] } } or { $replaceRoo...




What is Leadership

 




Spark Error - missing part 0 of the schema, 2 parts are expected

 Exception -  Caused by: org.apache.spark.sql.AnalysisException : Could not read schema from the hive metastore because it is corrupted. (missing part 0 of the schema, 2 parts are expected).; Analysis -  ·          Check for table definition. In TBLProperties, you might find something like this – > spark.sql.sources.schema.numPartCols > 'spark.sql.sources.schema.numParts' 'spark.sql.sources.schema.part.0' > 'spark.sql.sources.schema.part.1' 'spark.sql.sources.schema.part.2' > 'spark.sql.sources.schema.partCol.0' > 'spark.sql.sources.schema.partCol.1' That’s what error seems to say that part1 is defined but part0 is missing.  Solution -  Drop & re-create table. If Table was partitioned  then all partitions  would have been removed. So do either of below -  ·          Msck repair table <db_name>.<table_name> ·    ...




Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...




Read from a hive table and write back to it using spark sql

In context to Spark 2.2 - if we read from an hive table and write to same, we get following exception- scala > dy . write . mode ( "overwrite" ). insertInto ( "incremental.test2" ) org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; 1. This error means that our process is reading from same table and writing to same table. 2. Normally, this should work as process writes to directory .hiveStaging... 3. This error occurs in case of saveAsTable method, as it overwrites entire table instead of individual partitions. 4. This error should not occur with insertInto method, as it overwrites partitions not the table. 5. A reason why this happening is because Hive table has following Spark TBLProperties in its definition. This problem will solve for insertInto met...