[jira] [Commented] (SPARK-14768) Remove expectedType arg for PySpark Param

[ https://issues.apache.org/jira/browse/SPARK-14768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252280#comment-15252280 ] Jason C Lee commented on SPARK-14768: - Seems straightforward enough. I am working on the PR > Remove

[jira] [Commented] (SPARK-14564) Python Word2Vec missing setWindowSize method

[ https://issues.apache.org/jira/browse/SPARK-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237719#comment-15237719 ] Jason C Lee commented on SPARK-14564: - Looks straightforward enough. I will give it a shot! > Python

[jira] [Commented] (SPARK-13802) Fields order in Row(**kwargs) is not consistent with Schema.toInternal method

[ https://issues.apache.org/jira/browse/SPARK-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15216695#comment-15216695 ] Jason C Lee commented on SPARK-13802: - I tried making a fix where I treat a kwarg row as a dict, and

[jira] [Commented] (SPARK-13802) Fields order in Row(**kwargs) is not consistent with Schema.toInternal method

[ https://issues.apache.org/jira/browse/SPARK-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205446#comment-15205446 ] Jason C Lee commented on SPARK-13802: - I will give it a shot! Working on the PR at the moment. >

[jira] [Commented] (SPARK-12519) "Managed memory leak detected" when using distinct on PySpark DataFrame

[ https://issues.apache.org/jira/browse/SPARK-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15135630#comment-15135630 ] Jason C Lee commented on SPARK-12519: - The memory leak in question comes from a

[jira] [Commented] (SPARK-12683) SQL timestamp is wrong when accessed as Python datetime

[ https://issues.apache.org/jira/browse/SPARK-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102749#comment-15102749 ] Jason C Lee commented on SPARK-12683: - Looks like collect() eventually calls py4j's collectToPython,

[jira] [Commented] (SPARK-12683) SQL timestamp is wrong when accessed as Python datetime

[ https://issues.apache.org/jira/browse/SPARK-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15094877#comment-15094877 ] Jason C Lee commented on SPARK-12683: - For me on my machine it's an hour of difference. The

[jira] [Commented] (SPARK-12655) GraphX does not unpersist RDDs

[ https://issues.apache.org/jira/browse/SPARK-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090165#comment-15090165 ] Jason C Lee commented on SPARK-12655: - The VertexRDD and EdgeRDD you see are created during the

[jira] [Issue Comment Deleted] (SPARK-10943) NullType Column cannot be written to Parquet

[ https://issues.apache.org/jira/browse/SPARK-10943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason C Lee updated SPARK-10943: Comment: was deleted (was: I'd like to work on this. Thanx) > NullType Column cannot be written

[jira] [Commented] (SPARK-10943) NullType Column cannot be written to Parquet

[ https://issues.apache.org/jira/browse/SPARK-10943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945783#comment-14945783 ] Jason C Lee commented on SPARK-10943: - I'd like to work on this. Thanx > NullType Column cannot be

[jira] [Commented] (SPARK-10877) Assertions fail straightforward DataFrame job due to word alignment

[ https://issues.apache.org/jira/browse/SPARK-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943956#comment-14943956 ] Jason C Lee commented on SPARK-10877: - I ran your SparkFilterByKeyTest.scala from spark-shell but did

[jira] [Commented] (SPARK-10877) Assertions fail straightforward DataFrame job due to word alignment

[ https://issues.apache.org/jira/browse/SPARK-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944141#comment-14944141 ] Jason C Lee commented on SPARK-10877: - I enabled assertions by specifying either the following in my

[jira] [Commented] (SPARK-10925) Exception when joining DataFrames

[ https://issues.apache.org/jira/browse/SPARK-10925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944303#comment-14944303 ] Jason C Lee commented on SPARK-10925: - I removed your 2nd step "apply an UDF on column "name"" and

[jira] [Issue Comment Deleted] (SPARK-10925) Exception when joining DataFrames

[ https://issues.apache.org/jira/browse/SPARK-10925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason C Lee updated SPARK-10925: Comment: was deleted (was: I removed your 2nd step "apply an UDF on column "name"" and was able to

[jira] [Commented] (SPARK-10847) Pyspark - DataFrame - Optional Metadata with `None` triggers cryptic failure

[ https://issues.apache.org/jira/browse/SPARK-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943670#comment-14943670 ] Jason C Lee commented on SPARK-10847: - You're welcome! > Pyspark - DataFrame - Optional Metadata

[jira] [Commented] (SPARK-10847) Pyspark - DataFrame - Optional Metadata with `None` triggers cryptic failure

[ https://issues.apache.org/jira/browse/SPARK-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933707#comment-14933707 ] Jason C Lee commented on SPARK-10847: - I would like to work on this. > Pyspark - DataFrame -

[jira] [Commented] (SPARK-10847) Pyspark - DataFrame - Optional Metadata with `None` triggers cryptic failure

[ https://issues.apache.org/jira/browse/SPARK-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14934044#comment-14934044 ] Jason C Lee commented on SPARK-10847: - Instead of Py4JJavaError: An error occurred while calling

[jira] [Commented] (SPARK-8616) SQLContext doesn't handle tricky column names when loading from JDBC

[ https://issues.apache.org/jira/browse/SPARK-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14601569#comment-14601569 ] Jason C Lee commented on SPARK-8616: I would like to work on this. SQLContext