The Wayback Machine - https://web.archive.org/web/20210508171603/https://github.com/apache/iceberg/issues/2309
Skip to content

/ iceberg

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

Jump to bottom

Display Table Location in Spark SQL Properties #2309

Open
RussellSpitzer opened this issue Mar 9, 2021 · 8 comments
Open

Display Table Location in Spark SQL Properties #2309

RussellSpitzer opened this issue Mar 9, 2021 · 8 comments
Labels
good first issue

Comments

@RussellSpitzer
Copy link
Member

@RussellSpitzer RussellSpitzer commented Mar 9, 2021

I realized today that while you are able to set the location of an Iceberg Table in Spark3, you cannot then view that location using the standard SQL commands.

Maybe we should considering populating this in table properties?
@RussellSpitzer
Copy link
Member Author

@RussellSpitzer RussellSpitzer commented Mar 9, 2021

I would also tag this as "good first ticket" but I do not know how to add labels
@aokolnychyi
Copy link
Contributor

@aokolnychyi aokolnychyi commented Mar 10, 2021

I feel it will be useful.
@aokolnychyi
Copy link
Contributor

@aokolnychyi aokolnychyi commented Mar 10, 2021

@flyrain, would you be interested in working on this?
@aokolnychyi
Copy link
Contributor

@aokolnychyi aokolnychyi commented Mar 10, 2021

We need to check if this will have any possible implications.
@aokolnychyi
Copy link
Contributor

@aokolnychyi aokolnychyi commented Mar 10, 2021

As far as I see, Spark passes the location as a table property. I think we can fake it in SparkTable like we fake the provider and the current snapshot id.
@aokolnychyi
Copy link
Contributor

@aokolnychyi aokolnychyi commented Mar 10, 2021

I think we can simply adapt SparkTable$properties.
@RussellSpitzer
Copy link
Member Author

@RussellSpitzer RussellSpitzer commented Mar 10, 2021 •
edited

Totally agree, I was worried about it being mis used somewhere, but I think this is the right thing to do, and of course we should add it to "reserved properties" too because currently you can set this but it has no effect
@flyrain
Copy link
Contributor

@flyrain flyrain commented Mar 13, 2021

Looking at this.
@flyrain flyrain mentioned this issue Mar 13, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue
3 participants
@RussellSpitzer @flyrain @aokolnychyi