Github user viirya commented on a diff in the pull request: https://github.com/apache/spark/pull/15427#discussion_r83140093 --- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala --- @@ -1878,17 +1878,25 @@ class Dataset[T] private[sql]( def dropDuplicates(colNames: Seq[String]): Dataset[T] = withTypedPlan { val resolver = sparkSession.sessionState.analyzer.resolver val allColumns = queryExecution.analyzed.output - val groupCols = colNames.map { colName => - allColumns.find(col => resolver(col.name, colName)).getOrElse( + val groupCols = colNames.flatMap { colName => + // It is possibly there are more than one columns with the same name, + // so we call filter instead of find. + val cols = allColumns.filter(col => resolver(col.name, colName)) + if (cols.isEmpty) { throw new AnalysisException( --- End diff -- My thought is: When an user mistakenly gives wrong column to `Dataset.drop`, it can be easily found out. But for `Dataset.dropDuplicates`, it might be harder to figure out duplicate rows are still there. So to throw an explicit exception looks more proper to me.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org