Move keyword/tracking code from index_twitter_stream.py into a separate input file

Data4Democracy / discursive

Twitter topic search and indexing with Elasticsearch

21 stars 11 forks source link

Move keyword/tracking code from index_twitter_stream.py into a separate input file #2

Closed hadoopjax closed 7 years ago

hadoopjax commented 7 years ago

Rather than having the tracking topics we want to use against the Twitter streaming API stored in our codebase let's move them to an input file. So, as a user, I can point to a file (i.e. on S3 or locally) to use as a source for my keywords!

Bonus points if you want to move the Tweet counter (StreamListener self.limit) and any Elasticsearch configs to a user-managed config file!

jbrambleDC commented 7 years ago

I am going to jump on this. should we take in the file as a sys.argv?

jbrambleDC commented 7 years ago

This can be closed!

hadoopjax commented 7 years ago

Yay! thanks @jbrambleDC