sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Cecho" <jar...@apache.org>
Subject Re: Review Request: Sqoop User Guide's troubleshooting section should explain how to override the column mapping when importing a table from MySQL into Hive
Date Tue, 20 Mar 2012 20:42:50 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/#review6138
-----------------------------------------------------------


I did not yet try how MySQL JDBC driver will behave myself, but column defined as TINYINT(1)
might contain valid values in range 0-255 (in unsigned form). So if the driver is reporting
type BIT for such columns, then there must be some data truncation. Therefore I would suggest
extending this new section also for normal (non-hive) import case.

- Jarek


On 2012-03-20 20:10:41, Kathleen Ting wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/4357/
> -----------------------------------------------------------
> 
> (Updated 2012-03-20 20:10:41)
> 
> 
> Review request for Sqoop and Jarek Cecho.
> 
> 
> Summary
> -------
> 
> Updated documentation.
> 
> 
> This addresses bug SQOOP-463.
>     https://issues.apache.org/jira/browse/SQOOP-463
> 
> 
> Diffs
> -----
> 
>   ./src/docs/user/troubleshooting.txt 1300726 
> 
> Diff: https://reviews.apache.org/r/4357/diff
> 
> 
> Testing
> -------
> 
> Built docs and verified.
> 
> 
> Thanks,
> 
> Kathleen
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message