Github user merlintang commented on the issue:

    https://github.com/apache/spark/pull/15819
  
    yes, exactly. This path is only for spark 1.x. what i proposed here is that
    we need to use the code of spark 2.0.x o fix the bug of spark 1.x. you can
    see this message from the my previous replies. I do not want to change the
    code, since it will make the 1.x and 2.x in great different.
    
    On Sun, Dec 4, 2016 at 10:08 AM, Xiao Li <[email protected]> wrote:
    
    > *@gatorsmile* commented on this pull request.
    > ------------------------------
    >
    > In sql/hive/src/main/scala/org/apache/spark/sql/hive/
    > execution/InsertIntoHiveTable.scala
    > <https://github.com/apache/spark/pull/15819>:
    >
    > > +      } else {
    > +        inputPathName.substring(0, inputPathName.indexOf(stagingDir) + 
stagingDir.length)
    > +      }
    > +    val dir: Path =
    > +      fs.makeQualified(
    > +        new Path(stagingPathName + "_" + executionId + "-" + 
TaskRunner.getTaskRunnerID))
    > +    logDebug("Created staging dir = " + dir + " for path = " + inputPath)
    > +    try {
    > +      if (!FileUtils.mkdir(fs, dir, true, hadoopConf)) {
    > +        throw new IllegalStateException("Cannot create staging directory 
 '" + dir.toString + "'")
    > +      }
    > +      fs.deleteOnExit(dir)
    > +    }
    > +    catch {
    > +      case e: IOException =>
    > +        throw new RuntimeException(
    >
    > Almost all the codes in this PR are copied from the existing master. This
    > PR is just for branch 1.6
    >
    > —
    > You are receiving this because you were mentioned.
    > Reply to this email directly, view it on GitHub
    > <https://github.com/apache/spark/pull/15819>, or mute the thread
    > 
<https://github.com/notifications/unsubscribe-auth/ABXY-aaIs7Wx6ha3mvqrTVIxehcxGkaYks5rEwGKgaJpZM4KtFSt>
    > .
    >



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to