[GitHub] dongjoon-hyun commented on a change in pull request #23383: [SPARK-23817][SQL] Create file source V2 framework and migrate ORC read path

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23383: [SPARK-23817][SQL] Create file source V2 framework and migrate ORC read path URL: https://github.com/apache/spark/pull/23383#discussion_r247337185 ## File path:

[GitHub] dongjoon-hyun commented on a change in pull request #23383: [SPARK-23817][SQL] Create file source V2 framework and migrate ORC read path

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23383: [SPARK-23817][SQL] Create file source V2 framework and migrate ORC read path URL: https://github.com/apache/spark/pull/23383#discussion_r247337038 ## File path:

[GitHub] dongjoon-hyun commented on a change in pull request #23383: [SPARK-23817][SQL] Create file source V2 framework and migrate ORC read path

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23383: [SPARK-23817][SQL] Create file source V2 framework and migrate ORC read path URL: https://github.com/apache/spark/pull/23383#discussion_r247337038 ## File path:

[GitHub] AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453808971 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins removed a comment on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query URL: https://github.com/apache/spark/pull/22952#issuecomment-453808962 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453808972 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins removed a comment on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query URL: https://github.com/apache/spark/pull/22952#issuecomment-453808963 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query URL: https://github.com/apache/spark/pull/22952#issuecomment-453808962 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453808971 Merged build finished. Test PASSed. This is

[GitHub] AmplabJenkins commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query URL: https://github.com/apache/spark/pull/22952#issuecomment-453808963 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453808972 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] SparkQA removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
SparkQA removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453798520 **[Test build #101135 has

[GitHub] SparkQA commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
SparkQA commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-45380 **[Test build #101135 has

[GitHub] SparkQA commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query

2019-01-12 Thread GitBox
SparkQA commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query URL: https://github.com/apache/spark/pull/22952#issuecomment-453808680 **[Test build #101138 has

[GitHub] dongjoon-hyun commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query

2019-01-12 Thread GitBox
dongjoon-hyun commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query URL: https://github.com/apache/spark/pull/22952#issuecomment-453808655 Retest this please This is an

[GitHub] dongjoon-hyun commented on a change in pull request #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#discussion_r247336530 ## File path:

[GitHub] dongjoon-hyun commented on a change in pull request #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#discussion_r247336530 ## File path:

[GitHub] dongjoon-hyun commented on a change in pull request #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#discussion_r247336496 ## File path:

[GitHub] AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453807560 Merged build finished. Test PASSed.

[GitHub] SparkQA commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
SparkQA commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453807596 **[Test build #101137 has

[GitHub] AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453807563 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453807560 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453807563 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453807362 Test FAILed. Refer to this link for build results (access rights to CI server

[GitHub] dongjoon-hyun commented on a change in pull request #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#discussion_r247336260 ## File path:

[GitHub] AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453807359 Merged build finished. Test FAILed.

[GitHub] SparkQA removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
SparkQA removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453797564 **[Test build #101134 has

[GitHub] AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453807362 Test FAILed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453807359 Merged build finished. Test FAILed.

[GitHub] SparkQA commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
SparkQA commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453807293 **[Test build #101134 has

[GitHub] HeartSaVioR commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query

2019-01-12 Thread GitBox
HeartSaVioR commented on issue #22952: [SPARK-20568][SS] Provide option to clean up completed files in streaming query URL: https://github.com/apache/spark/pull/22952#issuecomment-453807134 Kindly reminder. This is an

[GitHub] HeartSaVioR commented on issue #23142: [SPARK-26170][SS] Add missing metrics in FlatMapGroupsWithState

2019-01-12 Thread GitBox
HeartSaVioR commented on issue #23142: [SPARK-26170][SS] Add missing metrics in FlatMapGroupsWithState URL: https://github.com/apache/spark/pull/23142#issuecomment-453807143 Kindly reminder. This is an automated message from

[GitHub] HeartSaVioR commented on issue #22138: [SPARK-25151][SS] Apply Apache Commons Pool to KafkaDataConsumer

2019-01-12 Thread GitBox
HeartSaVioR commented on issue #22138: [SPARK-25151][SS] Apply Apache Commons Pool to KafkaDataConsumer URL: https://github.com/apache/spark/pull/22138#issuecomment-453807137 Kindly reminder. This is an automated message

[GitHub] dongjoon-hyun commented on a change in pull request #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#discussion_r247336035 ## File path:

[GitHub] HeartSaVioR commented on a change in pull request #23260: [SPARK-26311][YARN] New feature: custom log URL for stdout/stderr

2019-01-12 Thread GitBox
HeartSaVioR commented on a change in pull request #23260: [SPARK-26311][YARN] New feature: custom log URL for stdout/stderr URL: https://github.com/apache/spark/pull/23260#discussion_r247335594 ## File path:

[GitHub] HeartSaVioR commented on issue #23260: [SPARK-26311][YARN] New feature: custom log URL for stdout/stderr

2019-01-12 Thread GitBox
HeartSaVioR commented on issue #23260: [SPARK-26311][YARN] New feature: custom log URL for stdout/stderr URL: https://github.com/apache/spark/pull/23260#issuecomment-453805982 Sorry to revisit this lately: I had to tackle some other tasks as well, so spent time to do simpler thing first.

[GitHub] dongjoon-hyun commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#discussion_r247335540 ## File path:

[GitHub] HeartSaVioR commented on issue #23369: [SPARK-26429][SS]add jdbc sink for Structured Streaming.

2019-01-12 Thread GitBox
HeartSaVioR commented on issue #23369: [SPARK-26429][SS]add jdbc sink for Structured Streaming. URL: https://github.com/apache/spark/pull/23369#issuecomment-453804885 Seems like: 1) this needs to wait and reflect newer DSv2. 2) According to

[GitHub] HeartSaVioR edited a comment on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure

2019-01-12 Thread GitBox
HeartSaVioR edited a comment on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure URL: https://github.com/apache/spark/pull/23527#issuecomment-453804394 Thanks @dongjoon-hyun for fixing missing spot! Looks like I confused between SparkConf and Spark**App**Conf. I

[GitHub] HeartSaVioR commented on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure

2019-01-12 Thread GitBox
HeartSaVioR commented on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure URL: https://github.com/apache/spark/pull/23527#issuecomment-453804394 Thanks @dongjoon-hyun for fixing missing spot! Looks like I confused between SparkConf and Spark*App*Conf. I couldn't

[GitHub] HyukjinKwon commented on issue #21135: [SPARK-24060][TEST] StreamingSymmetricHashJoinHelperSuite should initialize after SparkSession creation

2019-01-12 Thread GitBox
HyukjinKwon commented on issue #21135: [SPARK-24060][TEST] StreamingSymmetricHashJoinHelperSuite should initialize after SparkSession creation URL: https://github.com/apache/spark/pull/21135#issuecomment-453803977 Looks right but if it doesn't cause an actual problem now, let's fix it

[GitHub] deshanxiao commented on a change in pull request #23486: [SPARK-26457] Show hadoop configurations in HistoryServer environment tab

2019-01-12 Thread GitBox
deshanxiao commented on a change in pull request #23486: [SPARK-26457] Show hadoop configurations in HistoryServer environment tab URL: https://github.com/apache/spark/pull/23486#discussion_r247334277 ## File path: core/src/main/scala/org/apache/spark/status/api/v1/api.scala

[GitHub] AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453802096 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453802097 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453802097 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453802096 Merged build finished. Test PASSed.

[GitHub] SparkQA removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
SparkQA removed a comment on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453790515 **[Test build #101133 has

[GitHub] SparkQA commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category

2019-01-12 Thread GitBox
SparkQA commented on issue #23412: [SPARK-26477][CORE] Use ConfigEntry for hardcoded configs for unsafe category URL: https://github.com/apache/spark/pull/23412#issuecomment-453802011 **[Test build #101133 has

[GitHub] AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453801461 Test FAILed. Refer to this link for build results (access rights to CI

[GitHub] AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453801460 Merged build finished. Test FAILed.

[GitHub] AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453801460 Merged build finished. Test FAILed.

[GitHub] SparkQA commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
SparkQA commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453801425 **[Test build #101136 has

[GitHub] SparkQA removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
SparkQA removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800521 **[Test build #101136 has

[GitHub] AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453801461 Test FAILed. Refer to this link for build results (access rights to CI server

[GitHub] jzhuge commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
jzhuge commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#discussion_r247333601 ## File path:

[GitHub] felixcheung commented on issue #23347: allow building spark gpu docker images

2019-01-12 Thread GitBox
felixcheung commented on issue #23347: allow building spark gpu docker images URL: https://github.com/apache/spark/pull/23347#issuecomment-453800996 IMO we haven’t concluded what we are trying to do having Dockerfile in the release. We had some discussion last year. In any case, with

[GitHub] HyukjinKwon commented on issue #23391: [SPARK-26456][SQL] Cast date/timestamp to string by Date/TimestampFormatter

2019-01-12 Thread GitBox
HyukjinKwon commented on issue #23391: [SPARK-26456][SQL] Cast date/timestamp to string by Date/TimestampFormatter URL: https://github.com/apache/spark/pull/23391#issuecomment-453800952 Let's also update PR description. `spark.sql.legacy.timeParser.enabled` is now removed.

[GitHub] jzhuge commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
jzhuge commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#discussion_r247333601 ## File path:

[GitHub] AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800570 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800572 Test PASSed. Refer to this link for build results (access rights to CI

[GitHub] AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800570 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800572 Test PASSed. Refer to this link for build results (access rights to CI server

[GitHub] SparkQA commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
SparkQA commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800521 **[Test build #101136 has

[GitHub] HyukjinKwon commented on a change in pull request #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
HyukjinKwon commented on a change in pull request #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#discussion_r247333476 ## File path: python/pyspark/broadcast.py ## @@ -80,7

[GitHub] HyukjinKwon commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
HyukjinKwon commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800408 Let's give a shot for this in 3.0.0. Cloudpickle also changed its protocol a long ago

[GitHub] AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453656615 Can one of the admins verify this patch?

[GitHub] HyukjinKwon commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+)

2019-01-12 Thread GitBox
HyukjinKwon commented on issue #20691: [SPARK-18161] [Python] Allow pickle to serialize >4 GB objects when possible (Python 3.4+) URL: https://github.com/apache/spark/pull/20691#issuecomment-453800378 ok to test This is an

[GitHub] HyukjinKwon commented on a change in pull request #23518: [SPARK-26600] Update spark-submit usage message

2019-01-12 Thread GitBox
HyukjinKwon commented on a change in pull request #23518: [SPARK-26600] Update spark-submit usage message URL: https://github.com/apache/spark/pull/23518#discussion_r247333262 ## File path: core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ## @@

[GitHub] HyukjinKwon commented on issue #23519: [SPARK-26601][SQL] Make broadcast-exchange thread pool configurable

2019-01-12 Thread GitBox
HyukjinKwon commented on issue #23519: [SPARK-26601][SQL] Make broadcast-exchange thread pool configurable URL: https://github.com/apache/spark/pull/23519#issuecomment-453799619 Also, how was this patch tested? looks UT doesn't cover the current change.

[GitHub] HyukjinKwon commented on a change in pull request #23519: [SPARK-26601][SQL] Make broadcast-exchange thread pool configurable

2019-01-12 Thread GitBox
HyukjinKwon commented on a change in pull request #23519: [SPARK-26601][SQL] Make broadcast-exchange thread pool configurable URL: https://github.com/apache/spark/pull/23519#discussion_r247333148 ## File path:

[GitHub] HyukjinKwon commented on a change in pull request #23519: [SPARK-26601][SQL] Make broadcast-exchange thread pool configurable

2019-01-12 Thread GitBox
HyukjinKwon commented on a change in pull request #23519: [SPARK-26601][SQL] Make broadcast-exchange thread pool configurable URL: https://github.com/apache/spark/pull/23519#discussion_r247333106 ## File path:

[GitHub] asfgit closed pull request #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled

2019-01-12 Thread GitBox
asfgit closed pull request #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled URL: https://github.com/apache/spark/pull/23529 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the

[GitHub] AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453798609 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453798608 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453798609 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453798608 Merged build finished. Test PASSed. This is

[GitHub] HyukjinKwon commented on issue #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled

2019-01-12 Thread GitBox
HyukjinKwon commented on issue #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled URL: https://github.com/apache/spark/pull/23529#issuecomment-453798579 Merged to master. This is an

[GitHub] SparkQA commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
SparkQA commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453798520 **[Test build #101135 has

[GitHub] dongjoon-hyun commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#discussion_r247332753 ## File path:

[GitHub] dongjoon-hyun commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
dongjoon-hyun commented on a change in pull request #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#discussion_r247332753 ## File path:

[GitHub] AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453788541 Can one of the admins verify this patch?

[GitHub] dongjoon-hyun commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table

2019-01-12 Thread GitBox
dongjoon-hyun commented on issue #23530: [SPARK-26576][SQL] Broadcast hint not applied to partitioned table URL: https://github.com/apache/spark/pull/23530#issuecomment-453798325 ok to test This is an automated message from

[GitHub] AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453797627 Test PASSed. Refer to this link for build results (access rights to CI server

[GitHub] AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453797626 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453797626 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453797627 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] SparkQA commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories.

2019-01-12 Thread GitBox
SparkQA commented on issue #23416: [SPARK-26463][CORE] Use ConfigEntry for hardcoded configs for scheduler categories. URL: https://github.com/apache/spark/pull/23416#issuecomment-453797564 **[Test build #101134 has

[GitHub] AmplabJenkins removed a comment on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType URL: https://github.com/apache/spark/pull/23512#issuecomment-453797160 Merged build finished. Test PASSed.

[GitHub] AmplabJenkins commented on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType URL: https://github.com/apache/spark/pull/23512#issuecomment-453797163 Test PASSed. Refer to this link for build results (access rights to CI server

[GitHub] AmplabJenkins removed a comment on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType

2019-01-12 Thread GitBox
AmplabJenkins removed a comment on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType URL: https://github.com/apache/spark/pull/23512#issuecomment-453797163 Test PASSed. Refer to this link for build results (access rights to CI

[GitHub] AmplabJenkins commented on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType

2019-01-12 Thread GitBox
AmplabJenkins commented on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType URL: https://github.com/apache/spark/pull/23512#issuecomment-453797160 Merged build finished. Test PASSed.

[GitHub] SparkQA commented on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType

2019-01-12 Thread GitBox
SparkQA commented on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType URL: https://github.com/apache/spark/pull/23512#issuecomment-453797083 **[Test build #101132 has

[GitHub] SparkQA removed a comment on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType

2019-01-12 Thread GitBox
SparkQA removed a comment on issue #23512: [SPARK-26593][SQL] Use Proleptic Gregorian calendar in casting UTF8String to Date/TimestampType URL: https://github.com/apache/spark/pull/23512#issuecomment-453786298 **[Test build #101132 has

[GitHub] SparkQA removed a comment on issue #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled

2019-01-12 Thread GitBox
SparkQA removed a comment on issue #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled URL: https://github.com/apache/spark/pull/23529#issuecomment-453784427 **[Test build #4507 has

[GitHub] SparkQA commented on issue #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled

2019-01-12 Thread GitBox
SparkQA commented on issue #23529: [SPARK-26503][CORE][DOC][FOLLOWUP] Get rid of spark.sql.legacy.timeParser.enabled URL: https://github.com/apache/spark/pull/23529#issuecomment-453795960 **[Test build #4507 has

[GitHub] SparkQA commented on issue #20512: [SPARK-23182][CORE] Allow enabling TCP keep alive on the RPC connections

2019-01-12 Thread GitBox
SparkQA commented on issue #20512: [SPARK-23182][CORE] Allow enabling TCP keep alive on the RPC connections URL: https://github.com/apache/spark/pull/20512#issuecomment-453794591 **[Test build #4506 has

[GitHub] SparkQA removed a comment on issue #20512: [SPARK-23182][CORE] Allow enabling TCP keep alive on the RPC connections

2019-01-12 Thread GitBox
SparkQA removed a comment on issue #20512: [SPARK-23182][CORE] Allow enabling TCP keep alive on the RPC connections URL: https://github.com/apache/spark/pull/20512#issuecomment-453782753 **[Test build #4506 has

[GitHub] pgandhi999 commented on a change in pull request #23437: [SPARK-26524] If the application directory fails to be created on the SPARK_WORKER_…

2019-01-12 Thread GitBox
pgandhi999 commented on a change in pull request #23437: [SPARK-26524] If the application directory fails to be created on the SPARK_WORKER_… URL: https://github.com/apache/spark/pull/23437#discussion_r247331157 ## File path:

[GitHub] felixcheung commented on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure

2019-01-12 Thread GitBox
felixcheung commented on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure URL: https://github.com/apache/spark/pull/23527#issuecomment-453794268 I think we need it added to module and then only "execute the test" when the profile is set

[GitHub] felixcheung commented on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure

2019-01-12 Thread GitBox
felixcheung commented on issue #23527: [SPARK-26482][K8S][TEST][FOLLOWUP] Fix compile failure URL: https://github.com/apache/spark/pull/23527#issuecomment-453794227 looks like integration test is not in the module list

  1   2   3   4   >