I'm working with a Hadoop distribution that doesn't support 1.5 yet, we'll
be able to upgrade in probably two months. For now I'm seeing the same
issue with spark not recognizing an existing column name in many
hive-table-to-dataframe situations:
Py4JJavaError: An error occurred while calling o375.filter.
: org.apache.spark.sql.AnalysisException: resolved attributes *state_code*
missing from
latitude,country_code,tim_zone_desc,longitude,dma_durable_key,submarket,dma_
code,dma_desc,county,city,zip_code,*state_code*;
On Mon, Dec 7, 2015 at 3:52 PM, Davies Liu <dav...@databricks.com> wrote:
> Could you reproduce this problem in 1.5 or 1.6?
>
> On Sun, Dec 6, 2015 at 12:29 AM, YaoPau <jonrgr...@gmail.com> wrote:
> > If anyone runs into the same issue, I found a workaround:
> >
> >>>> df.where('state_code = "NY"')
> >
> > works for me.
> >
> >>>> df.where(df.state_code == "NY").collect()
> >
> > fails with the error from the first post.
> >
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Spark-SQL-1-3-not-finding-attribute-in-DF-tp25599p25600.html
> > Sent from the Apache Spark User List mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
> > For additional commands, e-mail: user-h...@spark.apache.org
> >
>
