Re: Camel Hbase

[VinothKR]

I tried exploring the code and what I found was,

The HBaseData from mappingStrategy is not having column name, column family
details in HRow 

CellMappingStrategy mappingStrategy =
endpoint.getCellMappingStrategyFactory().getStrategy(exchange.getIn());
HBaseData data = mappingStrategy.resolveModel(exchange.getIn());

and the HRow is again getting populated on 

for (HBaseRow hRow : data.getRows()) {
hRow.apply(rowModel);
if (HBaseConstants.PUT.equals(operation)) {
putOperations.add(createPut(hRow));
}

where column name, column family and value type are getting populated while
CamelHBaseValue is not in it.




--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Hbase-tp5780953p5781022.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel-hbase : scan operation

[A577127]

Ok, I found the answer to my question.

For people that might be asking the same, if there are multiple results, the
header of the output message will contain all of them in its header with
number suffixes (like CamelHBaseValue, CamelHBaseValue2,
CamelHBaseValue3...).



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-hbase-scan-operation-tp5752732p5752743.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-hbase dependency inconsistency

[Filippo Balicchia]

Hi Mark,
did you try servicemix 5.14 to check if with camel 2.13.3
the problem is resolved ?

Regards

--Filippo

2014-11-18 15:09 GMT+01:00 Mark Webb :
> Sorry for the cross-post, I'm not sure if this is a ServiceMix or Camel
> problem.
>
> I am working on some data routes that will push data to HBase within
> ServiceMix.  My development environment depends on Apache Camel 2.13.2,
> specifically the camel-hbase component version 2.13.2 depends on avro
> 1.5.3.  This is according to the dependency hierarchy that maven provides.
> I only have camel-base version 2.13.2 listed in my pom.xml and maven pulls
> in the dependencies.  I'm not specifically including avro.
>
> When I deploy the camel-hbase feature in ServiceMix 5.1.2 I get an error
> saying that I must deploy avro  >= 1.7.7.  So it seems like the same
> version of the camel-hbase component relies on 2 different versions of
> avro: 1.5.3 for development and 1.7.7 for deployment within ServiceMix.
>
> Is there any way to fix this problem?
>
> Thanks,
> Mark

Re: camel-hbase dependency inconsistency

[Sobkowiak, Krzysztof]

Hi Mark

There was a problem with camel-avro included in ServiceMix 5.1.2
(https://issues.apache.org/jira/browse/CAMEL-7655). The same problem
probably was for camel-hbase as it uses avro too. ServiceMix 5.1.4
includes the Camel version which fixes this problem. You should use the
new version.

But there is another known problem
(https://issues.apache.org/jira/browse/SM-2323) with freeze while
refreshing some bundles. I have tested installation of camel-hbase on
5.1.4 and I had this problem. You should add camel-hbase at the end of
featuresBoot in org.apache.karaf.features.cfg to solve this problem.
This problem will not occur in ServiceMix 5.3.x and later based on Karaf
2.4.x or Karaf 3.0.x

If you still need to use ServiceMix 5.1.2 ther is a workaround described
here
https://issues.apache.org/jira/browse/SM-2346?focusedCommentId=14083772&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14083772

I hope it helps to solve you problem

Regards
Krzysztof




On 18-Nov-2014 15:09, Mark Webb wrote:
> Sorry for the cross-post, I'm not sure if this is a ServiceMix or Camel
> problem.
>
> I am working on some data routes that will push data to HBase within
> ServiceMix.  My development environment depends on Apache Camel 2.13.2,
> specifically the camel-hbase component version 2.13.2 depends on avro
> 1.5.3.  This is according to the dependency hierarchy that maven provides.
> I only have camel-base version 2.13.2 listed in my pom.xml and maven pulls
> in the dependencies.  I'm not specifically including avro.
>
> When I deploy the camel-hbase feature in ServiceMix 5.1.2 I get an error
> saying that I must deploy avro  >= 1.7.7.  So it seems like the same
> version of the camel-hbase component relies on 2 different versions of
> avro: 1.5.3 for development and 1.7.7 for deployment within ServiceMix.
>
> Is there any way to fix this problem?
>
> Thanks,
> Mark
>

-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Technical Architect @ Capgemini | Committer @ ASF
Capgemini  | Software Solutions Center
 | Wroclaw
e-mail: krzys.sobkow...@gmail.com  |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: Camel-hbase : problem with qualifier "id"

[Christian Müller]

I can confirm this issue. I have raised a JIRA [1] and work on a fix.

[1] https://issues.apache.org/jira/browse/CAMEL-7547

Best,
Christian
-

Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Wed, Jun 25, 2014 at 11:33 AM, A577127 
wrote:

> Hello,
>
> I'm not sure if this is a bug or an "undocumented" feature so I put this
> here.
>
> When using camel-hbase's producer, if you want to use an HBase qualifier
> with the value "id", it doesn't work.
>
> For example : I have an HBase table "registrations" with a family "token"
> and a qualifier "id". To scan it, I use this route :
>
>
>
> However the result doesn't give the database values. I tryed with another
> qualifier and it worked fine.
>
> I found out that when the producer tries to resolve the input parameters,
> this instruction goes wrong :
>
>
>
> This should get a String with the value "id", but instead it gets the value
> of the breadcrumbID header which is "ID-L83577-52983-1403687981986-0-1".
>
> Thanks
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-hbase-problem-with-qualifier-id-tp5752781.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Re: Camel-hbase : problem with qualifier "id"

[Christian Müller]

The "issue" in your route is:
setHeader("CamelHBaseQualifier", simple("id", String.class))

try:
setHeader("CamelHBaseQualifier", constant("id", String.class))

because:
simple("id", String.class) is evaluated to the input message id as
described at [1].

[1] http://camel.apache.org/simple.html

Best,

Christian
-

Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Wed, Jun 25, 2014 at 11:33 AM, A577127 
wrote:

> Hello,
>
> I'm not sure if this is a bug or an "undocumented" feature so I put this
> here.
>
> When using camel-hbase's producer, if you want to use an HBase qualifier
> with the value "id", it doesn't work.
>
> For example : I have an HBase table "registrations" with a family "token"
> and a qualifier "id". To scan it, I use this route :
>
>
>
> However the result doesn't give the database values. I tryed with another
> qualifier and it worked fine.
>
> I found out that when the producer tries to resolve the input parameters,
> this instruction goes wrong :
>
>
>
> This should get a String with the value "id", but instead it gets the value
> of the breadcrumbID header which is "ID-L83577-52983-1403687981986-0-1".
>
> Thanks
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-hbase-problem-with-qualifier-id-tp5752781.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Re: Camel-hbase : problem with qualifier "id"

[Christian Müller]

Checkout the unit test, if you want:
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=commit;h=5e97f9238fc292cc6fde3d75d8b98d4b26b7e66d

Best,

Christian
-

Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Fri, Jun 27, 2014 at 12:44 PM, Christian Müller <
christian.muel...@gmail.com> wrote:

> The "issue" in your route is:
> setHeader("CamelHBaseQualifier", simple("id", String.class))
>
> try:
> setHeader("CamelHBaseQualifier", constant("id", String.class))
>
> because:
> simple("id", String.class) is evaluated to the input message id as
> described at [1].
>
> [1] http://camel.apache.org/simple.html
>
> Best,
>
> Christian
> -
>
> Software Integration Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Wed, Jun 25, 2014 at 11:33 AM, A577127 
> wrote:
>
>> Hello,
>>
>> I'm not sure if this is a bug or an "undocumented" feature so I put this
>> here.
>>
>> When using camel-hbase's producer, if you want to use an HBase qualifier
>> with the value "id", it doesn't work.
>>
>> For example : I have an HBase table "registrations" with a family "token"
>> and a qualifier "id". To scan it, I use this route :
>>
>>
>>
>> However the result doesn't give the database values. I tryed with another
>> qualifier and it worked fine.
>>
>> I found out that when the producer tries to resolve the input parameters,
>> this instruction goes wrong :
>>
>>
>>
>> This should get a String with the value "id", but instead it gets the
>> value
>> of the breadcrumbID header which is "ID-L83577-52983-1403687981986-0-1".
>>
>> Thanks
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Camel-hbase-problem-with-qualifier-id-tp5752781.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>