I agree with Josh. These tests are valuable , even if then can not be run on
Jenkins due to setup issues. It will be good to run them atleast manually, when
jdbc data source specific changes are made . Filed Jira for this problem.
https://issues.apache.org/jira/browse/SPARK-17473
> On Sep
That might be a reasonable and much more simpler approach to try... but if
we resolve these issues, we should make it part of some frequent build to
make sure the build don't regress and that the actual functionality don't
regress either. Let me look into this again...
On Wed, Sep 7, 2016 at 2:46
I think that these tests are valuable so I'd like to keep them. If
possible, though, we should try to get rid of our dependency on the Spotify
docker-client library, since it's a dependency hell nightmare. Given our
relatively simple use of Docker here, I wonder whether we could just write
some
It looks like there is nobody running these tests, and after some
dependency upgrades in Spark 2.0 this has stopped working. I have tried to
bring up this but I am having some issues with getting the right
dependencies loaded and satisfying the docker-client expectations.
The question then is:
Hi,
I am getting the following error , when I am trying to run jdbc docker
integration tests on my laptop. Any ideas , what I might be be doing wrong ?
build/mvn -Pyarn -Phadoop-2.6 -Dhadoop.version=2.6.0 -Phive-thriftserver
-Phive -DskipTests clean install
build/mvn
