[jira] [Comment Edited] (CALCITE-553) "mvn clean install" fails due to missing SqlParserImpl
[
https://issues.apache.org/jira/browse/CALCITE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141012#comment-15141012
]
Josh Elser edited comment on CALCITE-553 at 2/10/16 3:36 PM:
-
-Oh, I think this is actually a Maven bug. The documentation definitely says
that this should work, and upgrading to 3.3.9 does fix it.-
-I will find the necessary minimum version to get this working and add a maven
min-version enforcer statement for this.-
Argh, apparently it was just circumstantial.
was (Author: elserj):
Oh, I think this is actually a Maven bug. The documentation definitely says
that this should work, and upgrading to 3.3.9 does fix it.
I will find the necessary minimum version to get this working and add a maven
min-version enforcer statement for this.
> "mvn clean install" fails due to missing SqlParserImpl
> --
>
> Key: CALCITE-553
> URL: https://issues.apache.org/jira/browse/CALCITE-553
> Project: Calcite
> Issue Type: Bug
>Reporter: Julian Hyde
>Assignee: Josh Elser
>
> Every second time I call {mvn -DskipTests clean install} it fails with
> {code}[ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/jhyde/open1/calcite.2/core/src/main/java/org/apache/calcite/sql/parser/SqlParser.java:[24,42]
> cannot find symbol
> symbol: class SqlParserImpl
> location: package org.apache.calcite.sql.parser.impl
> [ERROR]
> /home/jhyde/open1/calcite.2/core/src/main/java/org/apache/calcite/sql/parser/SqlParser.java:[201,50]
> cannot find symbol
> symbol: variable SqlParserImpl
> location: class org.apache.calcite.sql.parser.SqlParser.ConfigBuilder
> [INFO] 2 errors{code}
> I think CALCITE-484 broke something; maybe the parser is not generated
> correctly if at the start of the mvn command (before clean) the parser
> already exists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CALCITE-553) "mvn clean install" fails due to missing SqlParserImpl
[
https://issues.apache.org/jira/browse/CALCITE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141012#comment-15141012
]
Josh Elser commented on CALCITE-553:
Oh, I think this is actually a Maven bug. The documentation definitely says
that this should work, and upgrading to 3.3.9 does fix it.
I will find the necessary minimum version to get this working and add a maven
min-version enforcer statement for this.
> "mvn clean install" fails due to missing SqlParserImpl
> --
>
> Key: CALCITE-553
> URL: https://issues.apache.org/jira/browse/CALCITE-553
> Project: Calcite
> Issue Type: Bug
>Reporter: Julian Hyde
>Assignee: Vladimir Sitnikov
>
> Every second time I call {mvn -DskipTests clean install} it fails with
> {code}[ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/jhyde/open1/calcite.2/core/src/main/java/org/apache/calcite/sql/parser/SqlParser.java:[24,42]
> cannot find symbol
> symbol: class SqlParserImpl
> location: package org.apache.calcite.sql.parser.impl
> [ERROR]
> /home/jhyde/open1/calcite.2/core/src/main/java/org/apache/calcite/sql/parser/SqlParser.java:[201,50]
> cannot find symbol
> symbol: variable SqlParserImpl
> location: class org.apache.calcite.sql.parser.SqlParser.ConfigBuilder
> [INFO] 2 errors{code}
> I think CALCITE-484 broke something; maybe the parser is not generated
> correctly if at the start of the mvn command (before clean) the parser
> already exists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CALCITE-1031) In prepared statement, CsvScannableTable.scan is called twice
[
https://issues.apache.org/jira/browse/CALCITE-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141690#comment-15141690
]
Julian Hyde commented on CALCITE-1031:
--
[~zhenw], I would like to commit soon. If you don't provide a pull request in
the next 2 days I will write a fix that does not use your changes. Please
create a pull request.
> In prepared statement, CsvScannableTable.scan is called twice
> -
>
> Key: CALCITE-1031
> URL: https://issues.apache.org/jira/browse/CALCITE-1031
> Project: Calcite
> Issue Type: Bug
> Components: avatica
>Affects Versions: 1.5.0
> Environment: jdk 1.8.0_20 linux mint 17.3
>Reporter: Anıl Chalil
>Assignee: zhen wang
>Priority: Minor
> Attachments: threads_report.txt, threads_report2.txt
>
>
> Hi,
> I just noticed something when i am playing with examples.
> {code}
> Class.forName("org.apache.calcite.jdbc.Driver")
> val properties: Properties = new Properties()
> properties.setProperty("caseSensitive","true")
> val connection = DriverManager.getConnection("jdbc:calcite:", properties)
> val calciteConnection=connection.unwrap(classOf[CalciteConnection])
> val schema= (new
> CsvSchemaFactory()).create(calciteConnection.getRootSchema,null,Map[String,AnyRef]("directory"
> -> "src/main/resources/csv","flavor" -> "scannable").asJava)
> calciteConnection.getRootSchema.add("TEST",schema)
> val statement2=calciteConnection.prepareStatement("select \"tarih\" from
> \"TEST\".\"timeseries\" where \"sensor\" = ?")
> statement2.setString(1,"sensor38")
> val resultSet1=statement2.executeQuery()
> while(resultSet1.next())
> println(resultSet1.getString("tarih"))
> {code}
> My example like above. But when i call executeQuery i noticed that
> CsvScannableTable.scan called twice and enumerator iterating on values. When
> i inspected stacktraces i found that one of the call come from
> AvaticaConnection.java:463 and the other one is AvaticaConnection:489 .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
