Skip to content

Conversation

@chris-allan
Copy link
Contributor

Add string metadata support and expand test cases accordingly.

/cc @kkoz, @erindiel

Copy link
Member

@Shelnutt2 Shelnutt2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

@Shelnutt2 Shelnutt2 requested a review from gsvic September 29, 2020 11:01
Copy link
Contributor

@gsvic gsvic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you @chris-allan!

@gsvic gsvic merged commit a198c04 into TileDB-Inc:master Sep 29, 2020
@chris-allan
Copy link
Contributor Author

👍 Thanks guys.

Only thought I had was whether String return values on read would be useful? Right now you have to know you'll get a byte[] back, what encoding was used, etc. How are you guys handling strings in the other languages? I look only briefly at the way TileDB-Py is doing this:

https://github.com/TileDB-Inc/TileDB-Py/blob/2c26865dbb10204430c349fe63c65d6a36035c78/tiledb/libmetadata.pyx#L53-L58

@gsvic
Copy link
Contributor

gsvic commented Sep 29, 2020

Hey @chris-allan -- Could you take a look at the Util class which provides a String manipulation method for turning bytes with offsets into a list of strings? This might be helpful https://github.com/TileDB-Inc/TileDB-Java/blob/master/src/main/java/io/tiledb/java/api/Util.java

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.

3 participants