Fei Wang created SPARK-50991:
Summary: Align the table schema column position beginning index
Key: SPARK-50991
URL: https://issues.apache.org/jira/browse/SPARK-50991
Project: Spark
Issue Type: Bu
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906985#comment-17906985
]
Fei Wang commented on SPARK-50620:
--
resolved by https://issues.apache.org/jira/browse/S
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang resolved SPARK-50620.
--
Resolution: Not A Problem
The issue has gone since 3.5.1, will check the patch in 3.5.1
> Dead lock c
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906950#comment-17906950
]
Fei Wang commented on SPARK-50620:
--
thanks [~wforget]
> Dead lock caused by SQLConf$
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Issue Type: Bug (was: Improvement)
> Dead lock caused by SQLConf$ and SqlApiConf initialization
> -
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Description:
{code:java}
"Executor 92 task launch worker for task 2910, task 69.0 in stage 7.0 (TID
291
Fei Wang created SPARK-50620:
Summary: Dead lock caused by SQLConf$ and SqlApiConf
Key: SPARK-50620
URL: https://issues.apache.org/jira/browse/SPARK-50620
Project: Spark
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Attachment: iceberg_compaction.txt
> Dead lock caused by SQLConf$ and SqlApiConf
> -
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Summary: Dead lock caused by SQLConf$ and SqlApiConf initialization (was:
Dead lock caused by SQLConf$
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Description:
{code:java}
"Executor 92 task launch worker for task 2910, task 69.0 in stage 7.0 (TID
291
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Description:
{code:java}
"Executor 92 task launch worker for task 2910, task 69.0 in stage 7.0 (TID
291
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Summary: Dead lock caused by SQLConf$ and SqlApiConf (was: Dead lock
caused by SQLConf$ and SqlApiConf
[
https://issues.apache.org/jira/browse/SPARK-50620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-50620:
-
Description:
"Executor 92 task launch worker for task 2910, task 69.0 in stage 7.0 (TID
2910)" #152 dae
Fei Wang created SPARK-46091:
Summary: [KUBERNETES] Respect the existing kubernetes container
SPARK_LOCAL_DIRS env
Key: SPARK-46091
URL: https://issues.apache.org/jira/browse/SPARK-46091
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-43540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43540:
-
Summary: Add working directory into classpath on the driver in K8S cluster
mode (was: Add current worki
[
https://issues.apache.org/jira/browse/SPARK-43540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43540:
-
Description:
In Yarn cluster modes, the passed files/jars are able to be accessed in the
classloader. L
[
https://issues.apache.org/jira/browse/SPARK-43540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43540:
-
Description:
In Yarn cluster modes, the passed files/jars are able to be accessed in the
classloader. L
[
https://issues.apache.org/jira/browse/SPARK-43540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43540:
-
Description:
In Yarn cluster modes, the passed files/jars are able to be accessed in the
classloader. L
Fei Wang created SPARK-43540:
Summary: Add current working directory into classpath on the
driver in K8S cluster mode
Key: SPARK-43540
URL: https://issues.apache.org/jira/browse/SPARK-43540
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-43504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43504:
-
Summary: [K8S] Mounts the hadoop config map on the executor pod (was:
[K8S] Mount hadoop config map in
[
https://issues.apache.org/jira/browse/SPARK-43504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43504:
-
Description:
Since SPARK-25815 [,|https://github.com/apache/spark/pull/22911,] the hadoop
config map wi
[
https://issues.apache.org/jira/browse/SPARK-43504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43504:
-
Description:
Since SPARK-25815 [,|https://github.com/apache/spark/pull/22911,] the hadoop
config map is
[
https://issues.apache.org/jira/browse/SPARK-43504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43504:
-
Description:
Since SPARK-25815 [,|https://github.com/apache/spark/pull/22911,] the hadoop
config map is
[
https://issues.apache.org/jira/browse/SPARK-43504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722674#comment-17722674
]
Fei Wang commented on SPARK-43504:
--
gentle ping [~vanzin] [~dongjoon] [~ifilonenko]
[
https://issues.apache.org/jira/browse/SPARK-43504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43504:
-
Description:
Since SPARK-25815 [,|https://github.com/apache/spark/pull/22911,] the hadoop
config map is
Fei Wang created SPARK-43504:
Summary: [K8S] Mount hadoop config map in executor side
Key: SPARK-43504
URL: https://issues.apache.org/jira/browse/SPARK-43504
Project: Spark
Issue Type: Improvemen
[
https://issues.apache.org/jira/browse/SPARK-43419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43419:
-
Description:
make limit.cores be able to be fallen back to request.cores
now without limit.cores, we wi
[
https://issues.apache.org/jira/browse/SPARK-43419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43419:
-
Description:
make limit.cores be able to be fallen back to request.cores
now without limit.cores, we wi
[
https://issues.apache.org/jira/browse/SPARK-43419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-43419:
-
Description:
make limit.cores be able to be fallen back to request.cores
now without limit.cores, we wi
Fei Wang created SPARK-43419:
Summary: [K8S] Make limit.cores be able to be fallen back to
request.cores
Key: SPARK-43419
URL: https://issues.apache.org/jira/browse/SPARK-43419
Project: Spark
Is
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965735#comment-15965735
]
Fei Wang commented on SPARK-20184:
--
Also use the master branch to test my test case:
1.
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965597#comment-15965597
]
Fei Wang edited comment on SPARK-20184 at 4/12/17 9:21 AM:
---
try
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965597#comment-15965597
]
Fei Wang edited comment on SPARK-20184 at 4/12/17 9:21 AM:
---
try
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965597#comment-15965597
]
Fei Wang commented on SPARK-20184:
--
try this :
1. create table
[code]
val df = (1 to 500
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965308#comment-15965308
]
Fei Wang commented on SPARK-20184:
--
Tested with a smaller table 100,000 rows.
Codegen on
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Summary: performance regression for complex/long sql when enable whole
stage codegen (was: performance r
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
The performance of following SQL get much worse in spark 2.x in contrast with
codegen off.
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
The performance of following SQL get much worse in spark 2.x in contrast with
codegen off.
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
The performance of following SQL get much worse in spark 2.x in contrast with
codegen off.
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
The performance of following SQL get much worse in spark 2.x in contrast with
codegen off.
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
The performance of following SQL get much worse in spark 2.x in contrast with
codegen off.
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
The performance of following SQL get much worse in spark 2.x in contrast with
codegen off.
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952123#comment-15952123
]
Fei Wang commented on SPARK-20184:
--
[~r...@databricks.com] [~davies] May be we need spli
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
Execute following sql with spark 2.x when codegen enabled, the performance is
much worse
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
Execute flowing sql with spark 2.x when codegen enabled, the performance is
much worse th
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
Execute flowing sql with spark 2.x when codegen enabled, the performance is
much worse th
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Summary: performance regression for complex/long sql when enable codegen
(was: performance regression fo
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
Execute flowing sql with spark 2.x when codegen enabled, the performance is
much worse th
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
Execute flowing sql with spark 2.x when codegen enabled, the performance is
much worse th
[
https://issues.apache.org/jira/browse/SPARK-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-20184:
-
Description:
Execute flowing sql with spark 2.x when codegen enabled, the performance is
much worse th
Fei Wang created SPARK-20184:
Summary: performance regression for complex sql when enable codegen
Key: SPARK-20184
URL: https://issues.apache.org/jira/browse/SPARK-20184
Project: Spark
Issue Type
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-17556:
-
Attachment: (was: executor broadcast.pdf)
> Executor side broadcast for broadcast joins
> ---
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-17556:
-
Attachment: executor broadcast.pdf
> Executor side broadcast for broadcast joins
> --
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-17556:
-
Attachment: executor broadcast.pdf
update design doc
> Executor side broadcast for broadcast joins
> ---
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-17556:
-
Attachment: (was: executor broadcast.pdf)
> Executor side broadcast for broadcast joins
> ---
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516772#comment-15516772
]
Fei Wang commented on SPARK-17556:
--
[~viirya] in this case how about notify driver to r
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516732#comment-15516732
]
Fei Wang commented on SPARK-17556:
--
That's a good point!
In your solution, the broadcas
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516639#comment-15516639
]
Fei Wang edited comment on SPARK-17556 at 9/23/16 2:50 PM:
---
Yes
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516639#comment-15516639
]
Fei Wang commented on SPARK-17556:
--
Yes, the main different is is does not introduce ove
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-17556:
-
Comment: was deleted
(was: Not correct, I just collect the broadcast ref to the driver but not the
data:
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516545#comment-15516545
]
Fei Wang commented on SPARK-17556:
--
Not correct, I just collect the broadcast ref to the
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516546#comment-15516546
]
Fei Wang commented on SPARK-17556:
--
Not correct, I just collect the broadcast ref to the
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516386#comment-15516386
]
Fei Wang edited comment on SPARK-17556 at 9/23/16 1:15 PM:
---
[~r
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516386#comment-15516386
]
Fei Wang edited comment on SPARK-17556 at 9/23/16 1:05 PM:
---
[~r
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516386#comment-15516386
]
Fei Wang commented on SPARK-17556:
--
[~rxin] attached a design doc for the executor based
[
https://issues.apache.org/jira/browse/SPARK-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-17556:
-
Attachment: executor broadcast.pdf
> Executor side broadcast for broadcast joins
> --
Fei Wang created SPARK-17644:
Summary: The failed stage never resubmitted due to abort stage in
another thread
Key: SPARK-17644
URL: https://issues.apache.org/jira/browse/SPARK-17644
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-12742:
-
Due Date: 11/Jan/16
Component/s: SQL
> org.apache.spark.sql.hive.LogicalPlanToSQLSuite failure due
[
https://issues.apache.org/jira/browse/SPARK-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-12742:
-
Summary: org.apache.spark.sql.hive.LogicalPlanToSQLSuite failure due to
Table already exists (was: org.a
[
https://issues.apache.org/jira/browse/SPARK-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-12742:
-
Summary: org.apache.spark.sql.hive.LogicalPlanToSQLSuite failure due to
(was: org.apache.spark.sql.hive
Fei Wang created SPARK-12742:
Summary: org.apache.spark.sql.hive.LogicalPlanToSQLSuite failuer
Key: SPARK-12742
URL: https://issues.apache.org/jira/browse/SPARK-12742
Project: Spark
Issue Type: B
Fei Wang created SPARK-1:
Summary: deserialize RoaringBitmap using Kryo serializer throw
Buffer underflow exception
Key: SPARK-1
URL: https://issues.apache.org/jira/browse/SPARK-1
Project: Spa
[
https://issues.apache.org/jira/browse/SPARK-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735995#comment-14735995
]
Fei Wang commented on SPARK-4131:
-
can you try the example of my test suite to see if it w
[
https://issues.apache.org/jira/browse/SPARK-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699075#comment-14699075
]
Fei Wang commented on SPARK-10030:
--
[~hyukjin.kwon] this is defenitly a spark sql bug, s
[
https://issues.apache.org/jira/browse/SPARK-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698974#comment-14698974
]
Fei Wang commented on SPARK-10030:
--
[~liancheng] can you have a look on this issue?
> M
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698124#comment-14698124
]
Fei Wang commented on SPARK-9725:
-
good job :)
> spark sql query string field return empt
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696449#comment-14696449
]
Fei Wang commented on SPARK-9725:
-
[~davies] please see the comment of peizhongshuai
> sp
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696324#comment-14696324
]
Fei Wang commented on SPARK-9725:
-
we test on suse and redhat, both has this issue.
Now we
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696323#comment-14696323
]
Fei Wang commented on SPARK-9725:
-
in some cases(the long table name) of ours it also show
[
https://issues.apache.org/jira/browse/SPARK-8890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679447#comment-14679447
]
Fei Wang commented on SPARK-8890:
-
should this be part of tungsten?
> Reduce memory consu
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662847#comment-14662847
]
Fei Wang commented on SPARK-9725:
-
And i not set SPARK_PREPEND_CLASSES
> spark sql query
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661389#comment-14661389
]
Fei Wang edited comment on SPARK-9725 at 8/7/15 6:21 AM:
-
i try th
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661389#comment-14661389
]
Fei Wang edited comment on SPARK-9725 at 8/7/15 6:21 AM:
-
i try th
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661389#comment-14661389
]
Fei Wang commented on SPARK-9725:
-
i try the master again and reproduce this issue:
M151:
[
https://issues.apache.org/jira/browse/SPARK-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661383#comment-14661383
]
Fei Wang commented on SPARK-9725:
-
how much memory you set to executor?
> spark sql query
Fei Wang created SPARK-9725:
---
Summary: spark sql query string field return empty/garbled string
Key: SPARK-9725
URL: https://issues.apache.org/jira/browse/SPARK-9725
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621935#comment-14621935
]
Fei Wang commented on SPARK-8968:
-
changed, how about this?
> dynamic partitioning in spa
[
https://issues.apache.org/jira/browse/SPARK-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang updated SPARK-8968:
Summary: dynamic partitioning in spark sql performance issue due to the
high GC overhead (was: shuffled by
Fei Wang created SPARK-8968:
---
Summary: shuffled by the partition clomns when dynamic
partitioning to optimize the memory overhead
Key: SPARK-8968
URL: https://issues.apache.org/jira/browse/SPARK-8968
Projec
[
https://issues.apache.org/jira/browse/SPARK-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576547#comment-14576547
]
Fei Wang commented on SPARK-7173:
-
is this resolved by spark-6470?
> Support YARN node la
[
https://issues.apache.org/jira/browse/SPARK-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang closed SPARK-7866.
---
Resolution: Won't Fix
Wrong print in intelli idea, this is really ok, not a problem.
> print the format strin
[
https://issues.apache.org/jira/browse/SPARK-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559048#comment-14559048
]
Fei Wang commented on SPARK-7866:
-
Get it, thanks Owen.
> print the format string in data
Fei Wang created SPARK-7866:
---
Summary: print the format string in dataframe explain
Key: SPARK-7866
URL: https://issues.apache.org/jira/browse/SPARK-7866
Project: Spark
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SPARK-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang resolved SPARK-3323.
-
Resolution: Fixed
> yarn website's Tracking UI links to the Standby RM
> -
[
https://issues.apache.org/jira/browse/SPARK-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang closed SPARK-5240.
---
Resolution: Won't Fix
> Adding `createDataSourceTable` interface to Catalog
>
[
https://issues.apache.org/jira/browse/SPARK-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang closed SPARK-6997.
---
Resolution: Won't Fix
> Convert StringType in LocalTableScan
> -
>
>
[
https://issues.apache.org/jira/browse/SPARK-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549924#comment-14549924
]
Fei Wang commented on SPARK-6997:
-
this is not nessarry since we have convert the data fro
[
https://issues.apache.org/jira/browse/SPARK-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fei Wang closed SPARK-7289.
---
Resolution: Won't Fix
use usually not write sql like this
> Combine Limit and Sort to avoid total ordering
>
Fei Wang created SPARK-7659:
---
Summary: Sort by attributes that are not present in the SELECT
clause when there is windowfunction analysis error
Key: SPARK-7659
URL: https://issues.apache.org/jira/browse/SPARK-7659
Fei Wang created SPARK-7656:
---
Summary: use CatalystConf in FunctionRegistry
Key: SPARK-7656
URL: https://issues.apache.org/jira/browse/SPARK-7656
Project: Spark
Issue Type: Improvement
Co
1 - 100 of 115 matches
Mail list logo
