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

"re-retrieving" sample data #13

Open
lars-petter-hauge opened this issue Feb 4, 2020 · 3 comments
Open

"re-retrieving" sample data #13

lars-petter-hauge opened this issue Feb 4, 2020 · 3 comments

Comments

@lars-petter-hauge
Copy link

I read #3

Yes, only the data that has not been already fetched (as in committed in transaction) is returned. So you should save training session data in your end when you read it.

Does this really mean that if one does not save the data, it is impossible to retrieve it again?

Could I ask why it is like this? Or, why would you not allow an application to get data more than once? (say, e.g. if user deletes whatever local content the application has stored)

@ftrojan
Copy link

ftrojan commented Apr 26, 2020

I am also interested to hear the answer here.

@fortysix2ahead
Copy link

I guess the answer is really „no, that’s not possible“. If you scan through the documentation, you will see that activities are accessed via their ids, but there is no chance to actually find out, what ids exist, like i.e. give me all ids between now and four weeks ago. The only way is to get „recent ones“. There is not even documentation what recent means.
Why this is the case remains a Polar mystery.

@mbalonso
Copy link

mbalonso commented May 7, 2022

After a couple of discussions with polar support, the best explanation they gave was that it was an attempt to protect their production environment that supports polar flow, etc. If they allowed devs to access the same api/infrastructure that polar uses, they run the risk of us disrupting their platform. Definitely frustrating, but I kind of get it.

They built a lightweight platform to provide devs access to this data, but purge the data once it is retrieved. This helps keeps storage costs down.

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

No branches or pull requests

4 participants