[ https://issues.apache.org/jira/browse/SPARK-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340202#comment-14340202 ]
Sean Owen commented on SPARK-4900: ---------------------------------- Hm, I tend to agree that upfront error checking is good, and infinite / NaN values are not valid as input. There's a bit of a question of where you check, and whether it slows things down a lot to be always checking. Would you care to propose error checking for this case? I suppose at least the error message for this ARPACK error could hint at this possible cause. > MLlib SingularValueDecomposition ARPACK IllegalStateException > -------------------------------------------------------------- > > Key: SPARK-4900 > URL: https://issues.apache.org/jira/browse/SPARK-4900 > Project: Spark > Issue Type: Bug > Components: MLlib > Affects Versions: 1.1.1, 1.2.0, 1.2.1 > Environment: Ubuntu 1410, Java HotSpot(TM) 64-Bit Server VM (build > 25.25-b02, mixed mode) > spark local mode > Reporter: Mike Beyer > Assignee: Sean Owen > Fix For: 1.3.0 > > > java.lang.reflect.InvocationTargetException > ... > Caused by: java.lang.IllegalStateException: ARPACK returns non-zero info = 3 > Please refer ARPACK user guide for error message. > at > org.apache.spark.mllib.linalg.EigenValueDecomposition$.symmetricEigs(EigenValueDecomposition.scala:120) > at > org.apache.spark.mllib.linalg.distributed.RowMatrix.computeSVD(RowMatrix.scala:235) > at > org.apache.spark.mllib.linalg.distributed.RowMatrix.computeSVD(RowMatrix.scala:171) > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org