Skip to content
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

Failed to resolve endpoint: twitter-search #377

Merged
merged 1 commit into from
Jan 25, 2019

Conversation

lburgazzoli
Copy link
Contributor

@lburgazzoli lburgazzoli commented Jan 24, 2019

fixes #370

This fixes this issue but there are still cases that are not
properly covered so assuming we have a route like this:

from("twitter-search:{{twitterKeywords}}?delay={{twitterDelayMs}}"
    + "&consumerKey={{twitterConsumerKey}}"
    + "&consumerSecret={{twitterConsumerSecret}}"
    + "&accessToken={{twitterAccessToken}}"
    + "&accessTokenSecret={{twitterAccessTokenSecret}}")

the operator will properly discovery the component but
the url will be truncated and will contains only:

twitter-search:{{twitterKeywords}}?delay={{twitterDelayMs}}

@lburgazzoli lburgazzoli merged commit fb419a4 into apache:master Jan 25, 2019
@lburgazzoli lburgazzoli deleted the github-370 branch January 27, 2019 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Failed to resolve endpoint: twitter-search
3 participants