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

Updated timestamp parsing in yahoo-finance rivers #92

Merged
merged 1 commit into from
Aug 19, 2015

Conversation

jaredweiss
Copy link
Contributor

Fixes #91

Since the returned timestamp is in UTC, it needs to be converted to the default timestamp by using moment.tz(...).

(Also removes an unnecessary line I must have missed during the code review.)

@rhyolight
Copy link
Collaborator

Perhaps a better way to fix this is to update the config.yml timestamp? Then no code change is necessary.

@jaredweiss
Copy link
Contributor Author

I think it makes more sense to have it tied to the NY timezone since that's the timezone the stock exchange is based on. It doesn't really seem to matter from a data perspective whether we use the UTC or New York timezone since they're effectively telling the same info.

I guess the bigger question is do we want the timezones to be representative of what the data is actually referring to (in this case stocks traded on the NYSE) or to just keep the formatting of the server that we pull the data from. This might not be the best case for the question, but what if the NY Traffic streams were originally in UTC? Would we leave them in UTC or convert them to be NY's timezone?

@rhyolight
Copy link
Collaborator

I think you're right. That is the reason I put timezone in the config in
the first place. Good catch.


Matt Taylor
OS Community Flag-Bearer
Numenta

On Wed, Aug 19, 2015 at 12:58 PM, Jared Weiss notifications@github.com
wrote:

I think it makes more sense to have it tied to the NY timezone since
that's the timezone the stock exchange is based on. It doesn't really seem
to matter from a data perspective whether we use the UTC or New York
timezone since they're effectively telling the same info.

I guess the bigger question is do we want the timezones to be
representative of what the data is actually referring to (in this case
stocks traded on the NYSE) or to just keep the formatting of the server
that we pull the data from. This might not be the best case for the
question, but what if the NY Traffic streams were originally in UTC? Would
we leave them in UTC or convert them to be NY's timezone?


Reply to this email directly or view it on GitHub
#92 (comment)
.

@jaredweiss
Copy link
Contributor Author

😃

rhyolight added a commit that referenced this pull request Aug 19, 2015
Updated timestamp parsing in yahoo-finance rivers
@rhyolight rhyolight merged commit 75fc091 into htm-community:master Aug 19, 2015
@rhyolight
Copy link
Collaborator

Deployed! Thanks.

@jaredweiss jaredweiss mentioned this pull request Aug 22, 2015
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.

2 participants