Regarding SQOOP-585

[Amit Sela <am...@infolinks.com>]

I think I get the same error trying to import from MySQL to HBase using
--query with join.
I'm using sqoop 1.4.4 and I see in JIRA that the issue is Unresolved.
Is there a reason why it was not fixed ? Is the patch working ? if so, why
not fixed on trunk ?

Thanks,
Amit.

Re: Regarding SQOOP-585

[Gwen Shapira <gs...@cloudera.com>]

The MySQL behavior is well known and documented. Since the patch was never
committed, I'm not surprised the bug is still around :)

The patch looks like it fixes the issue. It was not committed because we'd
like the patch to include a fix to printResultSet function too.

You can apply the patch on trunk, build and run that.
Also feel free to complete the patch and contribute, so we can fix it in
trunk.

Gwen





On Thu, Jun 5, 2014 at 1:08 PM, Amit Sela <am...@infolinks.com> wrote:

> That's the query in the command I try to execute:
>
> --query 'select sd.id,deal_type,value,dd1.dimension_value as
> product,ifnull(dd2.dimension_value,"ALL") as
> country_code,dd3.dimension_value as
> publisher_id,ifnull(dd4.dimension_value,-1) as site_index from
> test.signed_deals sd join test.deal_dimensions dd1 on sd.id = dd1.deal_id
> and dd1.dimension_id=1 left join test.deal_dimensions dd2 on sd.id =
> dd2.deal_id and dd2.dimension_id=2 join test.deal_dimensions dd3 on sd.id
> = dd3.deal_id and dd3.dimension_id=3 left join test.deal_dimensions dd4 on
> sd.id = dd4.deal_id and dd4.dimension_id=4 where $CONDITIONS'
>
> And that's the error I get:
> ERROR tool.ImportTool: Imported Failed: Duplicate Column identifier
> specified: 'dimension_value
>
> Thanks,
> Amit.
>
>
> On Thu, Jun 5, 2014 at 8:31 PM, Abraham Elmahrek <ab...@cloudera.com> wrote:
>
>> Hey there,
>>
>> Are you sure you're hitting this issue? Could you provide your Sqoop
>> command?
>>
>> -Abe
>>
>>
>> On Thu, Jun 5, 2014 at 7:00 AM, Amit Sela <am...@infolinks.com> wrote:
>>
>>> I think I get the same error trying to import from MySQL to HBase using
>>> --query with join.
>>> I'm using sqoop 1.4.4 and I see in JIRA that the issue is Unresolved.
>>> Is there a reason why it was not fixed ? Is the patch working ? if so,
>>> why not fixed on trunk ?
>>>
>>> Thanks,
>>> Amit.
>>>
>>
>>
>

Re: Regarding SQOOP-585

[Amit Sela <am...@infolinks.com>]

That's the query in the command I try to execute:

--query 'select sd.id,deal_type,value,dd1.dimension_value as
product,ifnull(dd2.dimension_value,"ALL") as
country_code,dd3.dimension_value as
publisher_id,ifnull(dd4.dimension_value,-1) as site_index from
test.signed_deals sd join test.deal_dimensions dd1 on sd.id = dd1.deal_id
and dd1.dimension_id=1 left join test.deal_dimensions dd2 on sd.id =
dd2.deal_id and dd2.dimension_id=2 join test.deal_dimensions dd3 on sd.id =
dd3.deal_id and dd3.dimension_id=3 left join test.deal_dimensions dd4 on
sd.id = dd4.deal_id and dd4.dimension_id=4 where $CONDITIONS'

And that's the error I get:
ERROR tool.ImportTool: Imported Failed: Duplicate Column identifier
specified: 'dimension_value

Thanks,
Amit.


On Thu, Jun 5, 2014 at 8:31 PM, Abraham Elmahrek <ab...@cloudera.com> wrote:

> Hey there,
>
> Are you sure you're hitting this issue? Could you provide your Sqoop
> command?
>
> -Abe
>
>
> On Thu, Jun 5, 2014 at 7:00 AM, Amit Sela <am...@infolinks.com> wrote:
>
>> I think I get the same error trying to import from MySQL to HBase using
>> --query with join.
>> I'm using sqoop 1.4.4 and I see in JIRA that the issue is Unresolved.
>> Is there a reason why it was not fixed ? Is the patch working ? if so,
>> why not fixed on trunk ?
>>
>> Thanks,
>> Amit.
>>
>
>

Re: Regarding SQOOP-585

[Abraham Elmahrek <ab...@cloudera.com>]

Hey there,

Are you sure you're hitting this issue? Could you provide your Sqoop
command?

-Abe


On Thu, Jun 5, 2014 at 7:00 AM, Amit Sela <am...@infolinks.com> wrote:

> I think I get the same error trying to import from MySQL to HBase using
> --query with join.
> I'm using sqoop 1.4.4 and I see in JIRA that the issue is Unresolved.
> Is there a reason why it was not fixed ? Is the patch working ? if so, why
> not fixed on trunk ?
>
> Thanks,
> Amit.
>