Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16326
We really need to improve the document, I think
---
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 user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16326
Based on the discussion in https://github.com/apache/spark/pull/15983, we
do not plan to add automatic table repairing. Let me close it first.
---
If your project is set up for it, you can
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16326
Oh I see, you're saying if there are old files for the partition, the
INSERT INTO will cause those to become visible. That is a little confusing.
---
If your project is set up for it, you can reply
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16326
> hive> select * from test;
>OK
>ddda
>c a
Isn't this showing that hive is appending to the table (ddd, a) as expected
with INSERT INTO?
For the (213, 0)
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16326
Instead of appending the new rows, Hive will overwrite the previous files
in the specified location, even if we are using `INSERT INTO`. See the output
```
hive> create table test(c1
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16326
If we want to make it consistent with the managed Hive serde table, the
existing behavior is still not the same.
```
scala> spark.sql(s"create table newTab (fieldOne long, partCol
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16326
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 user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16326
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70315/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16326
**[Test build #70315 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70315/testReport)**
for PR 16326 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16326
cc @ericl @cloud-fan @mallman
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16326
**[Test build #70315 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70315/testReport)**
for PR 16326 at commit
11 matches
Mail list logo
