[GitHub] zeppelin issue #3235: [ZEPPELIN-3864] Fix Travis tests
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3235 Can you please fix the tests then. We canât merge anything that will cause all PRs to fail in Travis. Even when they âshouldâ be ---
[GitHub] zeppelin issue #3250: [Zeppelin 3792] Zeppelin SPNEGO support
Github user VipinRathor commented on the issue: https://github.com/apache/zeppelin/pull/3250 All CI builds seem to have passed as per https://travis-ci.org/VipinRathor/zeppelin/builds/464561551 I don't know why this PR is showing 1 failed check. Can someone please help me out? ---
[jira] [Created] (ZEPPELIN-3903) Cannot build with Scala 2.11 due to old Flink-Runner dependency
Andrew Fernandes created ZEPPELIN-3903:
--
Summary: Cannot build with Scala 2.11 due to old Flink-Runner
dependency
Key: ZEPPELIN-3903
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3903
Project: Zeppelin
Issue Type: Bug
Reporter: Andrew Fernandes
{{./dev/change_scala_version.sh 2.11}}
{{mvn clean package -DskipTests -Pscala-2.11 -Pspark-2.3 -Pbuild-distr}}
*Result*
{{[INFO] Zeppelin: Scalding interpreter . SUCCESS [ 35.191
s]}}
{{[INFO] Zeppelin: Java interpreter . SUCCESS [ 3.525
s]}}
{{[INFO] Zeppelin: Beam interpreter . FAILURE [ 12.811
s]}}
{{[INFO] Zeppelin: Hazelcast Jet interpreter SKIPPED}}
{{[INFO] Zeppelin: Apache Geode interpreter . SKIPPED}}
{{[INFO] Zeppelin: web Application .. SKIPPED}}
{{[INFO] Zeppelin: Server ... SKIPPED}}
{{[INFO] Zeppelin: Jupyter Support .. SKIPPED}}
{{[INFO] Zeppelin: Plugins Parent ... SKIPPED}}
{{[INFO] Zeppelin: Plugin S3NotebookRepo SKIPPED}}
{{[INFO] Zeppelin: Plugin VFSNotebookRepo ... SKIPPED}}
{{[INFO] Zeppelin: Plugin GitNotebookRepo ... SKIPPED}}
{{[INFO] Zeppelin: Plugin GitHubNotebookRepo SKIPPED}}
{{[INFO] Zeppelin: Plugin AzureNotebookRepo . SKIPPED}}
{{[INFO] Zeppelin: Plugin GCSNotebookRepo ... SKIPPED}}
{{[INFO] Zeppelin: Plugin ZeppelinHubRepo ... SKIPPED}}
{{[INFO] Zeppelin: Plugin FileSystemNotebookRepo SKIPPED}}
{{[INFO] Zeppelin: Plugin StandardLauncher .. SKIPPED}}
{{[INFO] Zeppelin: Plugin SparkInterpreterLauncher .. SKIPPED}}
{{[INFO] Zeppelin: Packaging distribution ... SKIPPED}}
{{[INFO]
}}
{{[INFO] BUILD FAILURE}}
{{[INFO]
}}
{{[INFO] Total time: 10:21 min}}
{{[INFO] Finished at: 2018-12-07T00:35:38Z}}
{{[INFO]
}}
{{[ERROR] Failed to execute goal on project zeppelin-beam: Could not resolve
dependencies for project org.apache.zeppelin:zeppelin-beam:jar:0.9.0-SNAPSHOT:
Could not find artifact org.apache.beam:beam-runners-flink_2.11:jar:2.0.0 in
central (https://repo.maven.apache.org/maven2) -> [Help 1]}}
If you look at
[https://mvnrepository.com/artifact/org.apache.beam/beam-runners-flink] the
earliest version that supports Scala 2.11 is 2.3.0. The requested version 2.0.0
only supports Scala 2.10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] Hello Apache projects, I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org. ## Why this move? ## The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub. ## Timeframe for relocation ## Initially, we are asking that projects voluntarily request to move their repositories to gitbox, hence this email. The voluntary timeframe is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over. To have your project moved in this initial phase, you will need: - Consensus in the project (documented via the mailing list) - File a JIRA ticket with INFRA to voluntarily move your project repos over to gitbox (as stated, this is highly automated and will take between a minute and an hour, depending on the size and number of your repositories) To sum up the preliminary timeline; - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) relocation - January 9th -> February 6th: Mandated (coordinated) relocation - February 7th: All remaining repositories are mass migrated. This timeline may change to accommodate various scenarios. ## Using GitHub with ASF repositories ## When your project has moved, you are free to use either the ASF repository system (gitbox.apache.org) OR GitHub for your development and code pushes. To be able to use GitHub, please follow the primer at: https://reference.apache.org/committer/github We appreciate your understanding of this issue, and hope that your project can coordinate voluntarily moving your repositories in a timely manner. All settings, such as commit mail targets, issue linking, PR notification schemes etc will automatically be migrated to gitbox as well. With regards, Daniel on behalf of ASF Infra. PS:For inquiries, please reply to us...@infra.apache.org, not your project's dev list :-).
[GitHub] zeppelin issue #3244: [ZEPPELIN-3882] Neo4jInterpreter - Support Point and D...
Github user conker84 commented on the issue: https://github.com/apache/zeppelin/pull/3244 @zjffdu ping ---
[GitHub] zeppelin issue #3239: Zeppelin 3879: create "maxRows" and "rowsFetchSize" va...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3239 It is weird that I see another property `common.max_count` but it is never used in `JdbcInterpreter`. I think we just need to keep one and remove others. Personally I prefer `zeppelin.jdbc.maxRows` ---
[GitHub] zeppelin issue #3239: Zeppelin 3879: create "maxRows" and "rowsFetchSize" va...
Github user monsieurp commented on the issue: https://github.com/apache/zeppelin/pull/3239 @zjffdu: Hi! Fair enough. What do you want me to do then? Should I remove the `rowsFetchSize` property? ---
[GitHub] zeppelin issue #3239: Zeppelin 3879: create "maxRows" and "rowsFetchSize" va...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3239 ping @monsieurp ---
[GitHub] zeppelin issue #3235: [ZEPPELIN-3864] Fix Travis tests
Github user Savalek commented on the issue: https://github.com/apache/zeppelin/pull/3235 @felixcheung, these tests should fall, because `maven` incorrectly handled errors when testing through `npm`. This PR is only the first part of fixing problems. The second part is the correction of those tests that have been falling for a long time, but because of the bug of the `frontend maven plugin 1.4`, `travis` shows that the `npm` tests have passed, but in fact this is not the case. ---
