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.

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

time zone in bitnami/spark #76024

Open
MammadTavakoli opened this issue Jan 3, 2025 · 2 comments
Open

time zone in bitnami/spark #76024

MammadTavakoli opened this issue Jan 3, 2025 · 2 comments
Assignees
Labels
spark tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@MammadTavakoli
Copy link

Name and Version

bitnami/spark:3.5.4

What architecture are you using?

amd64

What steps will reproduce the bug?

I installing bitnami/spark version 3.5.4 in dokcer and ubuntu os.
I set the timezone in docker-compose file az TZ:Asia/Tehran.
when in the bash of the spark container i run date command it show correct date time but when i run cat /etc/timezone it show Etc/UTC .

when i want show the current_timestamp() it show the Etc/UTC not TZ:Asia/Tehran

What is the expected behavior?

when i want show the current_timestamp() i want it show the time zone of Asia/Tehran

What do you see instead?

it show the Etc/UTC not TZ:Asia/Tehran

Additional information

I set "spark.sql.session.timeZone": "Asia/Tehran" in pyspark config too but it not change any things

@MammadTavakoli MammadTavakoli added the tech-issues The user has a technical issue about an application label Jan 3, 2025
@github-actions github-actions bot added the triage Triage is needed label Jan 3, 2025
@carrodher carrodher added the spark label Jan 8, 2025
@carrodher
Copy link
Member

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and want to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please feel free to contact us if you have any questions or need assistance.

If you have any questions about the application, customizing its content, or using technology and infrastructure, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

@MammadTavakoli
Copy link
Author

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and want to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please feel free to contact us if you have any questions or need assistance.

If you have any questions about the application, customizing its content, or using technology and infrastructure, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

thanks for your replay. I found that the problem is that the delta lake save timestamp as utc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spark tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants