Hugo PT

My feedback

  1. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Data Warehouse » Polybase  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo PT shared this idea  · 
  2. 44 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Data Warehouse » Polybase  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo PT supported this idea  · 
    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...

  3. 70 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  SQL Data Warehouse » Polybase  ·  Flag idea as inappropriate…  ·  Admin →
    Hugo PT supported this idea  · 
    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.

Feedback and Knowledge Base