Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Stack Overflow by freedev
, 1 year ago
Reference '11E' is ambiguous, could be: 11E#20457, 11E#20458.;
via Stack Overflow by Bamqf
, 2 years ago
Reference 'Email' is ambiguous, could be: Email#350, Email#361.;
via Stack Overflow by srivathsava
, 9 months ago
via GitHub by hiltonmbr
, 1 year ago
Reference 'var' is ambiguous, could be: var#166, var#167.;
via GitHub by kevinushey
, 1 year ago
Reference 'var' is ambiguous, could be: var#6, var#7.;
via Stack Overflow by Zambezi
, 6 months ago
Reference 'count' is ambiguous, could be: count#6619, count#6629.;
org.apache.spark.sql.AnalysisException: Reference '11E' is ambiguous, could be: 11E#20457, 11E#20458.;	at org.apache.spark.sql.catalyst.plans.logical.LogicalPlan.resolve(LogicalPlan.scala:264)