6 votesHugo PT shared this idea ·
Thank you for the request. This item is currently on our backlog and under review. We will update the item when the status changes.Hugo PT commented
Another must have feature for Polybase that is missing. With Hive files grow over columns without changes in order, additional new columns (so easy) are null over history, and do not appear while tables structure remains unchanged (ignored, also very important feature related to this point). With Polybase everytime a file changes data starts missing! Actually it only works retrieving data that matches the defined structures 1-1...
Thank you for your request. I would like to understand if this request concerns SQL DW or SQL Server implementation of PolyBase?Hugo PT commented
In our corp it's a must have feature for Polybase that is missing. On large result sets we are making additional code to generate one table/partition, with a view to union results adding hardcoded the partitioned fields. It's extra work, extra risk of failure, etc. For smaller result sets we just use SSIS over Hive, less work and safer.