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
| Recently working with [NEC]("https://www.nec.com/") on a specific project, i encountered timezone issue in Apache superset. After detailed analyses i solved this issue, below are the analysis and steps to do it. | |
| Conditions: | |
| 1. Superset does all time related calculations in UTC format only. So, it is recommended for you to do the same. | |
| 2. if possible skip setting timeaware dates in db, as this can create un-neccesery complexity/confusion on/during conversions. | |
| 3. have a central timzezone on which all operation happens (read/calculations/write), and UTC is best for that. | |
| Steps to follow: | |
| 1. Superset consider its system's timezone as default timezone for its UI dates, like date range. So set your container's timzezone as your desired time zone. |
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
| #!/usr/bin/env bash | |
| # make tracker3 daemon non workable & idompotent | |
| # this script will reset its settings, and configure tracker3 daemon, to not let it do anyting. | |
| # if other code has dependency on this tracker, then it will not break, but we also do achieve our goal. | |
| # interpretation for org.freedesktop.Tracker3.Miner.Files enable-monitor from this file | |
| # https://gitlab.gnome.org/GNOME/tracker-miners/-/blob/master/src/miners/fs/tracker-config.c | |
| #Time in seconds before crawling filesystem (0->1000) |