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.

Sign up for GitHub

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

Jump to bottom

rethinkdb import does not handle unicode in CSV files #2963

Closed
Tryneus opened this issue Aug 26, 2014 · 2 comments
Closed

rethinkdb import does not handle unicode in CSV files #2963

Tryneus opened this issue Aug 26, 2014 · 2 comments
Assignees
@Tryneus
Milestone
1.14.1

Comments

@Tryneus
Copy link
Member

Tryneus commented Aug 26, 2014

I don't believe there is a standard for unicode in CSV, but since we export utf-8 in CSV, we should be able to read it back in.

In addition, supposedly the v1.14.0 backup scripts hang when connecting to a v1.13.x server. Investigate.

Reported by @nickpoorman in IRC.
@Tryneus Tryneus added this to the 1.14.x milestone Aug 26, 2014
@Tryneus Tryneus self-assigned this Aug 26, 2014
@Tryneus
Copy link
Member Author

Tryneus commented Aug 26, 2014

Fix for CSV is up in review 2020. I'm not sure it's worth investigating the interoperability of different versions, as there are query-language differences in the v1.13.x and v1.14.x scripts, and we can't get around that without r.version() (see #2698).

@Tryneus
Copy link
Member Author

Tryneus commented Sep 2, 2014

Approved and fixed in next in commit 3d82a67, cherry-picked into v1.14.x in commit 398f3e0. Will be in release 1.14.2. Thanks for reporting this, @nickpoorman!

@Tryneus Tryneus closed this as completed Sep 2, 2014
@AtnNn AtnNn modified the milestones: 1.14.1, 1.14.x Sep 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Tryneus Tryneus

Labels
None yet
Projects
None yet
Milestone
1.14.1
Development

No branches or pull requests
2 participants
@Tryneus @AtnNn