Skip to content

Conversation

@liancheng
Copy link
Contributor

Constructs like Hive TRANSFORM may generate malformed rows (via badly authored external scripts for example). I'm a bit hesitant to have this feature, since it introduces per-tuple cost when caching tables. However, considering caching tables is usually a one-time cost, this is probably worth having.

Review on Reviewable

@SparkQA
Copy link

SparkQA commented Mar 1, 2015

Test build #28144 has started for PR 4842 at commit b05dbff.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Mar 1, 2015

Test build #28144 has finished for PR 4842 at commit b05dbff.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28144/
Test PASSed.

@marmbrus
Copy link
Contributor

marmbrus commented Mar 2, 2015

Seems reasonable to me. Integer comparison should not be very expensive.

asfgit pushed a commit that referenced this pull request Mar 3, 2015
…hen caching tables

Constructs like Hive `TRANSFORM` may generate malformed rows (via badly authored external scripts for example). I'm a bit hesitant to have this feature, since it introduces per-tuple cost when caching tables. However, considering caching tables is usually a one-time cost, this is probably worth having.

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/apache/spark/4842)
<!-- Reviewable:end -->

Author: Cheng Lian <lian@databricks.com>

Closes #4842 from liancheng/spark-6082 and squashes the following commits:

b05dbff [Cheng Lian] Provides better error message for malformed rows when caching tables

(cherry picked from commit 1a49496)
Signed-off-by: Michael Armbrust <michael@databricks.com>
@asfgit asfgit closed this in 1a49496 Mar 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants