Github user javadba commented on the pull request:
https://github.com/apache/spark/pull/1586#issuecomment-51149151
@ueshin
I have git clone'd to a completely new area, and I reverted my last commit.
git clone https://github.com/javadba/spark.git strlen2
cd strlen2
git chckout strlen
git revert 22eddbce6a201c8f5b5c31859ceb972e60657377
mvn -DskipTests -Pyarn -Phive -Phadoop-2.3 clean compile package
mvn -Pyarn -Phive -Phadoop-2.3 test
-DwildcardSuites=org.apache.spark.sql.hive.execution.HiveQuerySuite,org.apache.spark.sql.SQLQuerySuite,org.apache.spark.sql.catalyst.expressions.ExpressionEvaluationSuite
I get precisely the same error:
HiveQuerySuite:
21:03:31.120 WARN org.apache.spark.util.Utils: Your hostname, mithril
resolves to a loopback address: 127.0.1.1; using 10.0.0.33 instead (on
interface eth0)
21:03:31.121 WARN org.apache.spark.util.Utils: Set SPARK_LOCAL_IP if
you need to bind to another address
21:03:37.294 WARN org.apache.hadoop.util.NativeCodeLoader: Unable to
load native-hadoop library for your platform... using builtin-java classes
where applicable
21:03:40.045 WARN com.jolbox.bonecp.BoneCPConfig: Max Connections < 1.
Setting to 20
21:03:49.464 WARN com.jolbox.bonecp.BoneCPConfig: Max Connections < 1.
Setting to 20
21:03:49.487 WARN org.apache.hadoop.hive.metastore.ObjectStore: Version
information not found in metastore. hive.metastore.schema.verification is not
enabled so recording the schema version 0.12.0
21:03:57.157 WARN com.jolbox.bonecp.BoneCPConfig: Max Connections < 1.
Setting to 20
21:03:57.593 WARN com.jolbox.bonecp.BoneCPConfig: Max Connections < 1.
Setting to 20
- single case
- double case
- case else null
- having no references
- boolean = number
- CREATE TABLE AS runs once
- between
- div
- division
*** RUN ABORTED ***
java.lang.StackOverflowError:
at
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1.apply(Parsers.scala:254)
at
scala.util.parsing.combinator.Parsers$$anon$3.apply(Parsers.scala:222)
at
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1.apply(Parsers.scala:254)
at
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1.apply(Parsers.scala:254)
at
scala.util.parsing.combinator.Parsers$$anon$3.apply(Parsers.scala:222)
at
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1.apply(Parsers.scala:254)
at
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1.apply(Parsers.scala:254)
at
scala.util.parsing.combinator.Parsers$$anon$3.apply(Parsers.scala:222)
at
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1.apply(Parsers.scala:254)
at
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1.apply(Parsers.scala:254)
Now, let's revert the revert :
git log
commit db09cd132c2d7e995287eea54f3415726934138c
Author: Stephen Boesch <javadba>
Date: Mon Aug 4 20:54:24 2014 -0700
Revert "Use Octet/Char_Len instead of Octet/Char_length due to
apparent preexisting spark ParserCombinator bug."
This reverts commit 22eddbce6a201c8f5b5c31859ceb972e60657377.
git revert db09cd132c2d7e995287eea54f3415726934138c
mvn -Pyarn -Phive -Phadoop-2.3 test
-DwildcardSuites=org.apache.spark.sql.hive.execution.HiveQuerySuite,org.apache.spark.sql.SQLQuerySuite,org.apache.spark.sql.catalyst.expressions.ExpressionEvaluationSuite
Now those three test sutes pass again (specifically HiveQuerySuite did not
fail)
And .. just to be *extra* sure here- that we can toggle between pass/fail
arbitrary # of times:
commit 602adedc9ca58d99957eb12bd91098ffe904604c
Author: Stephen Boesch <javadba>
Date: Mon Aug 4 21:18:53 2014 -0700
Revert "Revert "Use Octet/Char_Len instead of Octet/Char_length due
to apparent preexisting spark ParserCombinator bug.""
git revert 602adedc9ca58d99957eb12bd91098ffe904604c
And once again HiveQuerySuite fails with the same error.
So I have established clearly the following:
the strlen branch on my fork fails with SOF if we rollback the commit
that changes OCTET/CHAR_LENGTH -> OCTET/CHAR_LEN.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
