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

Extend Dataset API to support writing to files (not just reading) #15014

Closed
alexwal opened this Issue Nov 30, 2017 · 13 comments

Comments

Projects
None yet
3 participants
@alexwal

alexwal commented Nov 30, 2017

Just as we have a pipeline to read from files and convert them to output vectors/data via some model, It would be very useful to have a pipeline to take data and write it to files.

Otherwise, we have to use TFRecordWriters and a bit more code, but really much of this can be abstracted away, simplifying the data creation process, especially when writing to shards (as one might do using distributed Tensorflow).

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Dec 1, 2017

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Dec 20, 2017

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue? Please update the label and/or status accordingly.

1 similar comment
@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Jan 3, 2018

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue? Please update the label and/or status accordingly.

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Jan 18, 2018

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

3 similar comments
@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Feb 6, 2018

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Feb 20, 2018

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Mar 7, 2018

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Mar 25, 2018

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Apr 17, 2018

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented May 2, 2018

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented May 17, 2018

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Jun 2, 2018

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler

This comment has been minimized.

Member

tensorflowbutler commented Jun 17, 2018

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment