spark 2.3.1 insertinto remove value of fields and change it to null












0















I just upgrade my spark cluster from 2.2.1 to 2.3.1 in order to enjoy the feature of overwrite specific partitions. see link.



But ....
From some reason when I am testing it I get a very strange behavior see code:



import org.apache.spark.SparkConf
import org.apache.spark.sql.{SaveMode, SparkSession}
case class MyRow(partitionField: Int, someId: Int, someText: String)
object ExampleForStack2 extends App{
val sparkConf = new SparkConf()
sparkConf.set("spark.sql.sources.partitionOverwriteMode","dynamic")
sparkConf.setMaster(s"local[2]")
val spark = SparkSession.builder().config(sparkConf).getOrCreate()
val list1 = List(
MyRow(1, 1, "someText")
,MyRow(2, 2, "someText2")
)
val list2 = List(
MyRow(1, 1, "someText modified")
,MyRow(3, 3, "someText3")
)
val df = spark.createDataFrame(list1)
val df2 = spark.createDataFrame(list2)

df2.show(false)
df.write.partitionBy("partitionField").option("path","/tmp/tables/").saveAsTable("my_table")
df2.write.mode(SaveMode.Overwrite).insertInto("my_table")
spark.sql("select * from my_table").show(false)
}


And output:



+--------------+------+-----------------+
|partitionField|someId|someText |
+--------------+------+-----------------+
|1 |1 |someText modified|
|3 |3 |someText3 |
+--------------+------+-----------------+

+------+---------+--------------+
|someId|someText |partitionField|
+------+---------+--------------+
|2 |someText2|2 |
|1 |someText |1 |
|3 |3 |null |
|1 |1 |null |
+------+---------+--------------+


Why I get those nulls ?
It seems that fields were moved ? but why?



Thanks










share|improve this question



























    0















    I just upgrade my spark cluster from 2.2.1 to 2.3.1 in order to enjoy the feature of overwrite specific partitions. see link.



    But ....
    From some reason when I am testing it I get a very strange behavior see code:



    import org.apache.spark.SparkConf
    import org.apache.spark.sql.{SaveMode, SparkSession}
    case class MyRow(partitionField: Int, someId: Int, someText: String)
    object ExampleForStack2 extends App{
    val sparkConf = new SparkConf()
    sparkConf.set("spark.sql.sources.partitionOverwriteMode","dynamic")
    sparkConf.setMaster(s"local[2]")
    val spark = SparkSession.builder().config(sparkConf).getOrCreate()
    val list1 = List(
    MyRow(1, 1, "someText")
    ,MyRow(2, 2, "someText2")
    )
    val list2 = List(
    MyRow(1, 1, "someText modified")
    ,MyRow(3, 3, "someText3")
    )
    val df = spark.createDataFrame(list1)
    val df2 = spark.createDataFrame(list2)

    df2.show(false)
    df.write.partitionBy("partitionField").option("path","/tmp/tables/").saveAsTable("my_table")
    df2.write.mode(SaveMode.Overwrite).insertInto("my_table")
    spark.sql("select * from my_table").show(false)
    }


    And output:



    +--------------+------+-----------------+
    |partitionField|someId|someText |
    +--------------+------+-----------------+
    |1 |1 |someText modified|
    |3 |3 |someText3 |
    +--------------+------+-----------------+

    +------+---------+--------------+
    |someId|someText |partitionField|
    +------+---------+--------------+
    |2 |someText2|2 |
    |1 |someText |1 |
    |3 |3 |null |
    |1 |1 |null |
    +------+---------+--------------+


    Why I get those nulls ?
    It seems that fields were moved ? but why?



    Thanks










    share|improve this question

























      0












      0








      0








      I just upgrade my spark cluster from 2.2.1 to 2.3.1 in order to enjoy the feature of overwrite specific partitions. see link.



      But ....
      From some reason when I am testing it I get a very strange behavior see code:



      import org.apache.spark.SparkConf
      import org.apache.spark.sql.{SaveMode, SparkSession}
      case class MyRow(partitionField: Int, someId: Int, someText: String)
      object ExampleForStack2 extends App{
      val sparkConf = new SparkConf()
      sparkConf.set("spark.sql.sources.partitionOverwriteMode","dynamic")
      sparkConf.setMaster(s"local[2]")
      val spark = SparkSession.builder().config(sparkConf).getOrCreate()
      val list1 = List(
      MyRow(1, 1, "someText")
      ,MyRow(2, 2, "someText2")
      )
      val list2 = List(
      MyRow(1, 1, "someText modified")
      ,MyRow(3, 3, "someText3")
      )
      val df = spark.createDataFrame(list1)
      val df2 = spark.createDataFrame(list2)

      df2.show(false)
      df.write.partitionBy("partitionField").option("path","/tmp/tables/").saveAsTable("my_table")
      df2.write.mode(SaveMode.Overwrite).insertInto("my_table")
      spark.sql("select * from my_table").show(false)
      }


      And output:



      +--------------+------+-----------------+
      |partitionField|someId|someText |
      +--------------+------+-----------------+
      |1 |1 |someText modified|
      |3 |3 |someText3 |
      +--------------+------+-----------------+

      +------+---------+--------------+
      |someId|someText |partitionField|
      +------+---------+--------------+
      |2 |someText2|2 |
      |1 |someText |1 |
      |3 |3 |null |
      |1 |1 |null |
      +------+---------+--------------+


      Why I get those nulls ?
      It seems that fields were moved ? but why?



      Thanks










      share|improve this question














      I just upgrade my spark cluster from 2.2.1 to 2.3.1 in order to enjoy the feature of overwrite specific partitions. see link.



      But ....
      From some reason when I am testing it I get a very strange behavior see code:



      import org.apache.spark.SparkConf
      import org.apache.spark.sql.{SaveMode, SparkSession}
      case class MyRow(partitionField: Int, someId: Int, someText: String)
      object ExampleForStack2 extends App{
      val sparkConf = new SparkConf()
      sparkConf.set("spark.sql.sources.partitionOverwriteMode","dynamic")
      sparkConf.setMaster(s"local[2]")
      val spark = SparkSession.builder().config(sparkConf).getOrCreate()
      val list1 = List(
      MyRow(1, 1, "someText")
      ,MyRow(2, 2, "someText2")
      )
      val list2 = List(
      MyRow(1, 1, "someText modified")
      ,MyRow(3, 3, "someText3")
      )
      val df = spark.createDataFrame(list1)
      val df2 = spark.createDataFrame(list2)

      df2.show(false)
      df.write.partitionBy("partitionField").option("path","/tmp/tables/").saveAsTable("my_table")
      df2.write.mode(SaveMode.Overwrite).insertInto("my_table")
      spark.sql("select * from my_table").show(false)
      }


      And output:



      +--------------+------+-----------------+
      |partitionField|someId|someText |
      +--------------+------+-----------------+
      |1 |1 |someText modified|
      |3 |3 |someText3 |
      +--------------+------+-----------------+

      +------+---------+--------------+
      |someId|someText |partitionField|
      +------+---------+--------------+
      |2 |someText2|2 |
      |1 |someText |1 |
      |3 |3 |null |
      |1 |1 |null |
      +------+---------+--------------+


      Why I get those nulls ?
      It seems that fields were moved ? but why?



      Thanks







      scala apache-spark






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 2 at 21:32









      Ehud LevEhud Lev

      8381017




      8381017
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Ok found it, insert into is based on fields position. see documentation




          Unlike saveAsTable, insertInto ignores the column names and just uses position-based resolution. For example:




          scala> Seq((1, 2)).toDF("i", "j").write.mode("overwrite").saveAsTable("t1")
          scala> Seq((3, 4)).toDF("j", "i").write.insertInto("t1")
          scala> Seq((5, 6)).toDF("a", "b").write.insertInto("t1")
          scala> sql("select * from t1").show
          +---+---+
          | i| j|
          +---+---+
          | 5| 6|
          | 3| 4|
          | 1| 2|
          +---+---+



          Because it inserts data to an existing table, format or options will
          be ignored.




          Moreover I am using dynamic partition which should appear as the last field. So the solution is to move the dynamic partitions to the end of the dataframe, which means in my case:



          df2.select("someId", "someText","partitionField").write.mode(SaveMode.Overwrite).insertInto("my_table")






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54013434%2fspark-2-3-1-insertinto-remove-value-of-fields-and-change-it-to-null%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Ok found it, insert into is based on fields position. see documentation




            Unlike saveAsTable, insertInto ignores the column names and just uses position-based resolution. For example:




            scala> Seq((1, 2)).toDF("i", "j").write.mode("overwrite").saveAsTable("t1")
            scala> Seq((3, 4)).toDF("j", "i").write.insertInto("t1")
            scala> Seq((5, 6)).toDF("a", "b").write.insertInto("t1")
            scala> sql("select * from t1").show
            +---+---+
            | i| j|
            +---+---+
            | 5| 6|
            | 3| 4|
            | 1| 2|
            +---+---+



            Because it inserts data to an existing table, format or options will
            be ignored.




            Moreover I am using dynamic partition which should appear as the last field. So the solution is to move the dynamic partitions to the end of the dataframe, which means in my case:



            df2.select("someId", "someText","partitionField").write.mode(SaveMode.Overwrite).insertInto("my_table")






            share|improve this answer




























              0














              Ok found it, insert into is based on fields position. see documentation




              Unlike saveAsTable, insertInto ignores the column names and just uses position-based resolution. For example:




              scala> Seq((1, 2)).toDF("i", "j").write.mode("overwrite").saveAsTable("t1")
              scala> Seq((3, 4)).toDF("j", "i").write.insertInto("t1")
              scala> Seq((5, 6)).toDF("a", "b").write.insertInto("t1")
              scala> sql("select * from t1").show
              +---+---+
              | i| j|
              +---+---+
              | 5| 6|
              | 3| 4|
              | 1| 2|
              +---+---+



              Because it inserts data to an existing table, format or options will
              be ignored.




              Moreover I am using dynamic partition which should appear as the last field. So the solution is to move the dynamic partitions to the end of the dataframe, which means in my case:



              df2.select("someId", "someText","partitionField").write.mode(SaveMode.Overwrite).insertInto("my_table")






              share|improve this answer


























                0












                0








                0







                Ok found it, insert into is based on fields position. see documentation




                Unlike saveAsTable, insertInto ignores the column names and just uses position-based resolution. For example:




                scala> Seq((1, 2)).toDF("i", "j").write.mode("overwrite").saveAsTable("t1")
                scala> Seq((3, 4)).toDF("j", "i").write.insertInto("t1")
                scala> Seq((5, 6)).toDF("a", "b").write.insertInto("t1")
                scala> sql("select * from t1").show
                +---+---+
                | i| j|
                +---+---+
                | 5| 6|
                | 3| 4|
                | 1| 2|
                +---+---+



                Because it inserts data to an existing table, format or options will
                be ignored.




                Moreover I am using dynamic partition which should appear as the last field. So the solution is to move the dynamic partitions to the end of the dataframe, which means in my case:



                df2.select("someId", "someText","partitionField").write.mode(SaveMode.Overwrite).insertInto("my_table")






                share|improve this answer













                Ok found it, insert into is based on fields position. see documentation




                Unlike saveAsTable, insertInto ignores the column names and just uses position-based resolution. For example:




                scala> Seq((1, 2)).toDF("i", "j").write.mode("overwrite").saveAsTable("t1")
                scala> Seq((3, 4)).toDF("j", "i").write.insertInto("t1")
                scala> Seq((5, 6)).toDF("a", "b").write.insertInto("t1")
                scala> sql("select * from t1").show
                +---+---+
                | i| j|
                +---+---+
                | 5| 6|
                | 3| 4|
                | 1| 2|
                +---+---+



                Because it inserts data to an existing table, format or options will
                be ignored.




                Moreover I am using dynamic partition which should appear as the last field. So the solution is to move the dynamic partitions to the end of the dataframe, which means in my case:



                df2.select("someId", "someText","partitionField").write.mode(SaveMode.Overwrite).insertInto("my_table")







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 2 at 21:51









                Ehud LevEhud Lev

                8381017




                8381017
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54013434%2fspark-2-3-1-insertinto-remove-value-of-fields-and-change-it-to-null%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith