New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Per tap configuration for cascading #146
Comments
@Antwnis I copied your email here in its own issue. I'll use this issue to track the per Thanks! |
Regarding the 'unknown problem just created #150 |
@Antwnis can you please try the latest snapshot (#333). It brings per tap configuration - both in terms of index/query but also complete settings (through the Cheers. |
Excellent work @costin !! Everything works as expected - Many thanks !! |
Glad to hear it - thanks for the feedback! |
Taken from #134
I'm using 1.3.0.M2 & Scalding 0.9.0rc4
I'm overriding the config object and set the
es.mapping.id
to "number"My Scalding Job looks like that
And the wrapper that i'm trying to implement and contribute to Scalding for the ElasticSearchSource currently looks like this:
My problem is that once i introduce :
I'm getting
My second concern is around the usage of the
ConfigurationOptions.ES_MAPPING_ID
as part of theJobConfiguration
I understand the benefits of that approach , for Hive/Pig, but I think for Cascading/Scalding - having a single property is inefficient
What i would ideally be able to do in Scalding is the following:
So i would like within a Single Job to have multiple elastic-search sources & sinks.
My understanding at the moment is that elasticsearch-hadoop will not allow me to configure all sources..
Anyhow i'm just looking for some help in implementing this capability in Scalding ..
Any help appreciated
The text was updated successfully, but these errors were encountered: