Basic knowledge of Treasure Data, including the Toolbelt
A Twitter developer application with the consumer key and consumer secret.
Treasure Data configured in the Twitter dev environment. Refer to:
Authorized Treasure Data account access
- Our Connector uses Twitter API v1.1 that requires Elevated access as Twitter API access level.
- If you were approved for a developer account before November 15th, 2021, you were automatically converted to Elevated access. This means that your existing Apps can continue to be used to make requests to standard v1.1, premium v1.1, and enterprise endpoints, and that all of your user Access Tokens are still valid.
Establish a Twitter Dev Environment for Treasure Data
The `cron` parameter accepts these options: `@hourly`, `@daily` and `@monthly`.
By default, schedule is setup in UTC timezone. You can set the schedule in a timezone using -t or --timezone option. The `--timezone` option only supports extended timezone formats like 'Asia/Tokyo', 'America/Los_Angeles' etc. Timezone abbreviations like PST, CST are *not* supported and may lead to unexpected schedules.
$ td connector:create \ daily_import \ "10 0 * * *" \ td_sample_db \ td_sample_table \ load.yml