Hi Sandra,
That's not an error but a reminder (which we probably should refactor
later) says the feed will try to use the configurations from the feed
definition. You don't really need to extend the access of your Twitter dev
account. As long as you follow the DDL template in the doc, you should be
fine. Here is the snippet from the documentation [1]:
use feeds;
create feed TwitterFeed with {
"adapter-name": "push_twitter",
"type-name": "Tweet",
"format": "twitter-status",
"consumer.key": "************",
"consumer.secret": "************",
"access.token": "**********",
"access.token.secret": "*************"
};
Best,
Xikui
On Fri, Apr 5, 2019 at 8:08 AM [email protected] <
[email protected]> wrote:
> Hi!
>
> When using the built-in push-based Twitter adapter, which endpoint in the
> Twitter API is it actually making a request to? I have obtained a developer
> account at Twitter, but I am not sure if I need any extended access than
> what provided for the normal developer accounts in order to use the Twitter
> adapter.
>
> When trying to start the feed which uses the Twitter adapter, I find the
> following error in the cc.log, and the query never seem to finish its
> execution:
>
> [QueryTranslator] WARN org.apache.asterix.external.util.TwitterUtil -
> unable to load authentication credentials from auth.properties
> filecredential information will be obtained from adapter's configuration
>
> Thanks in advance!
>
> Sandra
>
