MINOR: [Docs] Document tzdata behaviour on non-FHS systems#49253
Open
shr3yas-k wants to merge 2 commits intoapache:mainfrom
Open
MINOR: [Docs] Document tzdata behaviour on non-FHS systems#49253shr3yas-k wants to merge 2 commits intoapache:mainfrom
shr3yas-k wants to merge 2 commits intoapache:mainfrom
Conversation
github-actions
bot
added
Component: Documentation
awaiting review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
Timezone-related failures can occur on non-FHS-compliant systems when the
system timezone database is not discoverable. This behavior is currently
not documented, which may lead contributors to interpret such failures as
Arrow bugs.
What changes are included in this PR?
Add a section on the install.rst titled 'tzdata on non FHS-compliant systems' and explaining what goes wrong.
Are these changes tested?
No.
Are there any user-facing changes?
No. Changed docs.
*Github Issue: #49172 (Closes this)