maropu edited a comment on issue #25287: [SPARK-28552][SQL]Identification of 
different dialects insensitive to case by JDBC URL prefix
URL: https://github.com/apache/spark/pull/25287#issuecomment-546353231
 
 
   Have you checked the jenkins log?
   ```
   [info] Generating 
/home/jenkins/workspace/SparkPullRequestBuilder/target/javaunidoc/org/apache/spark/sql/jdbc/AggregatedDialect.html...
   [error] 
/home/jenkins/workspace/SparkPullRequestBuilder/sql/core/target/java/org/apache/spark/sql/jdbc/JdbcDialect.java:44:
 error: invalid entity ,
   [error]    * The tag of the database, it must be lowercase,the 
subsequent will match
   [error]                                                   ^
   [error] 
/home/jenkins/workspace/SparkPullRequestBuilder/sql/core/target/java/org/apache/spark/sql/jdbc/JdbcDialect.java:47:
 error: bad use of '>'
   [error]    * mysql  url:  jdbc:mysql://localhost/db  --> mysql
   [error]                                                ^
   [error] 
/home/jenkins/workspace/SparkPullRequestBuilder/sql/core/target/java/org/apache/spark/sql/jdbc/JdbcDialect.java:48:
 error: bad use of '>'
   [error]    * oracle url:  jdbc:oracle://localhost/db --> oracle
   [error]                                                ^
   [error] 
/home/jenkins/workspace/SparkPullRequestBuilder/sql/core/target/java/org/apache/spark/sql/jdbc/JdbcDialect.java:49:
 error: bad use of '>'
   [error]    * db2    url:  jdbc:db2://localhost/db    --> db2
   [error]                                                ^
   [info] Generating 
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to