[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-09-21 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/14600 Yes @avulanov can you close it? we can't close it directly and the bot can only close PRs opened vs master. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-09-20 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/14600 @srowen Do you mind if I ask this is supposed to be closed (as it is merged into 2.0)? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-09-17 Thread Praveenmail2him
Github user Praveenmail2him commented on the issue: https://github.com/apache/spark/pull/14600 Can anyone post the sample usage for this exception in Spark 2.0, I'm still facing this exception? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/14600 You can take a look at the JIRA -- would be in 2.0.1 or 2.1.0 whichever comes first. It could be a month or two before one of those happens. There's a workaround in the JIRA though. --- If your

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread tOverney
Github user tOverney commented on the issue: https://github.com/apache/spark/pull/14600 When can we expect a spark release with those changes incorporated? --- 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

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/14600 Thanks @avulanov for the follow up. Merging to 2.0 --- 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

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14600 Merged build finished. Test PASSed. --- 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

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14600 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63604/ Test PASSed. ---

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14600 **[Test build #63604 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63604/consoleFull)** for PR 14600 at commit

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14600 **[Test build #63604 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63604/consoleFull)** for PR 14600 at commit

[GitHub] spark issue #14600: [SPARK-15899] [SQL] Fix the construction of the file pat...

2016-08-11 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/14600 Jenkins test this please --- 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