[jira] [Commented] (SQOOP-3289) Add .travis.yml
[
https://issues.apache.org/jira/browse/SQOOP-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377212#comment-16377212
]
Attila Szabo commented on SQOOP-3289:
-
Hi Daniel,
Though in general the ASF community is great, IMHO it does not make too much
sense to compare one project to the other. Especially a very busy active like
Spark with something quite mature as Sqoop.
Though I think my message was clear enough, it's up to you if you willing to
wait until the current builds.apache.org build pipeline will do the real job.
Just one comment on my side :
If we won't be able to make the life of the contributors ( and the committers)
easier, any efforts on this front could be in vain.
My 2 cents,
Attila
> Add .travis.yml
> ---
>
> Key: SQOOP-3289
> URL: https://issues.apache.org/jira/browse/SQOOP-3289
> Project: Sqoop
> Issue Type: Task
> Components: build
>Affects Versions: 1.4.7
>Reporter: Daniel Voros
>Assignee: Daniel Voros
>Priority: Minor
> Fix For: 1.5.0
>
>
> Adding a .travis.yml would enable running builds/tests on travis-ci.org.
> Currently if you wish to use Travis for testing your changes, you have to
> manually add a .travis.yml to your branch. Having it committed to trunk would
> save us this extra step.
> I currently have an example
> [{{.travis.yml}}|https://github.com/dvoros/sqoop/blob/93a4c06c1a3da1fd5305c99e379484507797b3eb/.travis.yml]
> on my travis branch running unit tests for every commit and every pull
> request: https://travis-ci.org/dvoros/sqoop/builds
> Later we could add the build status to the project readme as well, see:
> https://github.com/dvoros/sqoop/tree/travis
> Also, an example of a pull request: https://github.com/dvoros/sqoop/pull/1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SQOOP-3289) Add .travis.yml
[
https://issues.apache.org/jira/browse/SQOOP-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377022#comment-16377022
]
Daniel Voros commented on SQOOP-3289:
-
Thanks for your response [~maugli]. I definitely agree with you, we should
automate all tests (including thirdparty+manual integration tests) and static
analysis checks as part of a CI gate.
AFAIK ASF is pretty flexible in this matter. For example, Spark's running
checks on a 3rd party Jenkins on PR hooks, while Hive and Hadoop trigger jobs
in builds.apache.org Jenkins via Jira attached patches.
None of them do the CI via Travis tho.
[Hive|https://github.com/apache/hive/blob/master/.travis.yml#L45] and
[Spark|https://github.com/apache/spark/blob/master/.travis.yml#L46] have
.travis.ymls but they're not even running tests. I guess that's because of the
50 min limitation on travis-ci.org runs.
I think we should deal with Travis and CI gatekeeping as separate tasks, and
open a new Jira for the CI part. What do you think?
BTW, I've just found out that we're already running this job on Jira
attachments, but it seems to fail recently. (:
https://builds.apache.org/job/PreCommit-SQOOP-Build/
> Add .travis.yml
> ---
>
> Key: SQOOP-3289
> URL: https://issues.apache.org/jira/browse/SQOOP-3289
> Project: Sqoop
> Issue Type: Task
> Components: build
>Affects Versions: 1.4.7
>Reporter: Daniel Voros
>Assignee: Daniel Voros
>Priority: Minor
> Fix For: 1.5.0
>
>
> Adding a .travis.yml would enable running builds/tests on travis-ci.org.
> Currently if you wish to use Travis for testing your changes, you have to
> manually add a .travis.yml to your branch. Having it committed to trunk would
> save us this extra step.
> I currently have an example
> [{{.travis.yml}}|https://github.com/dvoros/sqoop/blob/93a4c06c1a3da1fd5305c99e379484507797b3eb/.travis.yml]
> on my travis branch running unit tests for every commit and every pull
> request: https://travis-ci.org/dvoros/sqoop/builds
> Later we could add the build status to the project readme as well, see:
> https://github.com/dvoros/sqoop/tree/travis
> Also, an example of a pull request: https://github.com/dvoros/sqoop/pull/1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SQOOP-1904) support for DB2 XML data type when importing to hdfs
[ https://issues.apache.org/jira/browse/SQOOP-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376928#comment-16376928 ] Szabolcs Vasas commented on SQOOP-1904: --- Hi [~rush27], I think the best you can do then is to apply this patch on 1.4.6 release and build Sqoop yourself, but I am not sure it will cleanly apply since 1.4.6 is a quite old release. I am afraid that without this patch you cannot make the DB2 XML type work with Sqoop. Szabolcs > support for DB2 XML data type when importing to hdfs > > > Key: SQOOP-1904 > URL: https://issues.apache.org/jira/browse/SQOOP-1904 > Project: Sqoop > Issue Type: Improvement > Components: connectors >Affects Versions: 1.4.5 > Environment: RedHat6.4 + Sqoop1.4.5 + Hadoop 2.4.1 + Hive 0.14.0 + > DB2 10.5 >Reporter: xieshiju >Assignee: Ying Cao >Priority: Major > Labels: features > Fix For: 1.4.7 > > Attachments: SQOOP-1904.2.patch, SQOOP-1904.3.patch, > SQOOP-1904.4.patch, SQOOP-1904.5.patch, SQOOP-1904.6.patch, > SQOOP-1904.7.patch, SQOOP-1904.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > The DB2 connector should add XML data type support otherwise you will get an > error that Hive does not support the SQL type. > Example with column DESCRIPTION data type XML: > $SQOOP_HOME/bin/sqoop create-hive-table --connect > 'jdbc:db2://xxx.svl.ibm.com:6/SAMPLE' --username db2inst1 --password > db2inst1 --hive-table product_ct --table PRODUCT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
