Skip to main content

Hive QL Spark SQL - Transform Rows into Columns

By Dinesh

 

For a Structured Tabular Structure it is many a times required to transform Rows into Columns. This blog explains step by step process which can be executed as one SQL to achieve same. 

Lets try to understand with help of below example: where -in , we want to implement / transform input Table into table structure mentioned as output.


INPUT_TABLE 

topic
groupId
batchTimeMs
Partition 
offset 
Count 
t1 g001 1658173779 0123 122
t1g001 1658173779 12231100
t2g001 1658173779 01211

OUTPUT_TABLE 

rowkey:key

offset:0

count:0    

offset:1 

count:1 

t1:g001:1658173779 1231222231100

t2:g001:1658173779 

1211NULLNULL

 



FIRST STEP -

  • Concat Topic, GroupID, and BatchTimeMS to create RowKey 
  • Create Columns - offsets:0, counts:0, offsets:1, counts:1. Such that Columns has value only when respective partition value matches with column name.
  • SQL as below -

select concat_ws(':', topic,groupId,batchTimeMs) as rowkey,

case when partition='0' then offset else null end as `offsets:0`,

case when partition='0' then count else null end as `counts:0`,

case when partition='1' then offset else null end as `offsets:1`,

case when partition='1' then count else null end as `counts:1`

FROM INPUT_TABLE



rowkey

offset:0

count:0    

offset:1 

count:1 

t1:g001:1658173779 123122NULLNULL
t1:g001:1658173779NULLNULL2231100

t2:g001:1658173779 

1211NULLNULL




SECOND STEP-

  • Bring in all values of a ROWKEY in to one row. 
  • SQL as below -
select rowkey as `rowkey:key`,
collect_set(`offsets:0`)  as `offsets:0`,
collect_set(`counts:0`)  as `counts:0`,
collect_set(`offsets:1`)  as `offsets:1`,
collect_set(`counts:1`)  as `counts:1` FROM (
select concat_ws(':', topic,groupId,batchTimeMs) as rowkey,
case when partition='0' then offset else null end as `offsets:0`,
case when partition='0' then count else null end as `counts:0`,
case when partition='1' then offset else null end as `offsets:1`,
case when partition='1' then count else null end as `counts:1`
FROM INPUT_TABLE ) T1 group by rowkey

rowkey:key

offset:0

count:0    

offset:1 

count:1 

t1:g001:1658173779 [123, NULL][122, NULL][2231,NULL][100,NULL]

t2:g001:1658173779 

[12][11][NULL][NULL]



THIRD STEP - 
  • Select only first value from Array of values.
  • SQL as below resulting in final desired output - 
select rowkey as `rowkey:key`,
collect_set(`offsets:0`) [0] as `offsets:0`,
collect_set(`counts:0`) [0] as `counts:0`,
collect_set(`offsets:1`) [0] as `offsets:1`,
collect_set(`counts:1`) [0] as `counts:1` FROM (
select concat_ws(':', topic,groupId,batchTimeMs) as rowkey,
case when partition='0' then offset else null end as `offsets:0`,
case when partition='0' then count else null end as `counts:0`,
case when partition='1' then offset else null end as `offsets:1`,
case when partition='1' then count else null end as `counts:1`
FROM INPUT_TABLE ) T1 group by rowkey

rowkey:key

offset:0

count:0    

offset:1 

count:1 

t1:g001:1658173779 1231222231100

t2:g001:1658173779 

1211NULLNULL

Comments

Post a Comment

Popular posts

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

By Dinesh
  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...
Post a Comment
Read more




Scala Spark building Jar leads java.lang.StackOverflowError

By Dinesh
  Exception -  [Thread-3] ERROR scala_maven.ScalaCompileMojo - error: java.lang.StackOverflowError [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.TraversableForwarder$class.isEmpty(TraversableForwarder.scala:36) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.isEmpty(ListBuffer.scala:45) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.toList(ListBuffer.scala:306) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.result(ListBuffer.scala:300) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:31) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:27) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.GenericCompanion.apply(GenericCompanion.scala:50) [Thread-3] INFO scala_maven.ScalaCompile...
Post a Comment
Read more




MongoDB Chunk size many times bigger than configure chunksize (128 MB)

By Dinesh
  Shard Shard_0 at Shard_0/xyz.com:27018 { data: '202.04GiB', docs: 117037098, chunks: 5, 'estimated data per chunk': '40.4GiB', 'estimated docs per chunk': 23407419 } --- Shard Shard_1 at Shard_1/abc.com:27018 { data: '201.86GiB', docs: 116913342, chunks: 4, 'estimated data per chunk': '50.46GiB', 'estimated docs per chunk': 29228335 } Per MongoDB-  Starting in 6.0.3, we balance by data size instead of the number of chunks. So the 128MB is now only the size of data we migrate at-a-time. So large data size per chunk is good now, as long as the data size per shard is even for the collection. refer -  https://www.mongodb.com/community/forums/t/chunk-size-many-times-bigger-than-configure-chunksize-128-mb/212616 https://www.mongodb.com/docs/v6.0/release-notes/6.0/#std-label-release-notes-6.0-balancing-policy-changes
Post a Comment
Read more




AWS EMR Spark – Much Larger Executors are Created than Requested

By Dinesh
  Starting EMR 5.32 and EMR 6.2 you can notice that Spark can launch much larger executors that you request in your job settings. For example - We started a Spark Job with  spark.executor.cores  =   4 But, one can see that the executors with 20 cores (instead of 4 as defined by spark.executor.cores) were launched. The reason for allocating larger executors is that there is a AWS specific Spark option spark.yarn.heterogeneousExecutors.enabled (exists in EMR only, does not exist in Open Source Spark) that is set to true by default that combines multiple executor creation requests on the same node into a larger executor container. So as the result you have fewer executor containers than you expected, each of them has more memory and cores that you specified. If you disable this option (--conf "spark.yarn.heterogeneousExecutors.enabled=false"), EMR will create containers with the specified spark.executor.memory and spark.executor.cores settings and will not co...
Post a Comment
Read more




Hive Count Query not working

By Dinesh
Hive with Tez execution engine -  count(*) not working , returning 0 results.  Solution -  set hive.compute.query.using.stats=false Refer -  https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties hive.compute.query.using.stats Default Value:  false Added In: Hive 0.13.0 with  HIVE-5483 When set to true Hive will answer a few queries like min, max, and count(1) purely using statistics stored in the metastore. For basic statistics collection, set the configuration property  hive.stats.autogather   to true. For more advanced statistics collection, run ANALYZE TABLE queries.
Post a Comment
Read more