Based on the recent discussion this is a vote thread to determine if we should include the Oracle connector into the core Sqoop code. I will be doing the bulk of the work to migrate it into the Sqoop codebase - and Jarcec has said he will assist me where required.
 +1 Yes - Oracle connector code should be moved into Sqoop code  +0 Abstain - I don't have a preference  -1 No - Oracle connector should remain separate from Sqoop
I am unsure why a vote is required for a code contribution - really just having it attached to a jira, and a committer pushing it should be enough. Either way, a big +1! Thanks, Hari On Friday, January 24, 2014 at 3:38 PM, David Robson wrote:
Thanks Venkat On Fri, Jan 24, 2014 at 5:12 PM, Abhijeet Gaikwad <[EMAIL PROTECTED]>wrote: CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Also +1. Good stuff. On Fri, Jan 24, 2014 at 9:21 PM, Venkat Ranganathan < [EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext