To automatically retrieve historical data from DataSift, create a new Fetch Task by following these steps. The connector runs each fetch task automatically, based on the schedule that is configured in the configuration file.
To create a new Fetch Task
In the [FetchTasks]
section of the configuration file, specify the number of fetch tasks using the Number
parameter. If you are configuring the first fetch task, type Number=1
. If one or more fetch tasks have already been configured, increase the value of the Number
parameter by one (1). Below the Number
parameter, specify the names of the fetch tasks, starting from zero (0). For example:
[FetchTasks] Number=1 0=Historic
Below the [FetchTasks]
section, create a new TaskName section. The name of the section must match the name of the new fetch task. For example:
[FetchTasks] Number=1 0=Historic [Historic]
In the new section, set the following parameters so that the connector can access the DataSift repository.
DatasiftUsername
|
The user name to use to authenticate with DataSift. |
DatasiftApiKey
|
The API key that is used to authenticate with DataSift. |
For example:
[Historic] DatasiftUsername=username DatasiftApiKey=APIkey
You can retrieve historic data through a subscription:
To retrieve historic data through a subscription, set the configuration parameter SubscriptionID
. For example:
[Historic] DatasiftUsername=username DatasiftApiKey=APIkey SubscriptionID=65faf9e9a428dbe61feb763057cc7cff
To retrieve historic data by specifying the source and time period, set either StreamDefinition
or StreamHash
. Then, set the parameters HistoricsSources
, HistoricsStartTimeUtc
, and HistoricsEndTimeUtc
. For example:
[Historic] DatasiftUsername=username DatasiftApiKey=APIkey StreamHash=da99eaed1d9255477de4367306e2ae2b HistoricsSources=twitter HistoricsStartTimeUtc=2014-Apr-30 11:00:00 HistoricsEndTimeUtc=2014-Apr-30 13:00:00
Save and close the configuration file.
You can now start the connector.
|