Update we added 2024 07 11T17 36 17 685+00 00 The part for t GoodData #gooddata-cloud

Join Slack

Update: we added "2024-07-11T17:36:17.685+00:00" T...

# gooddata-cloud

Doug Creighton

09/10/2024, 6:43 PM

Update: we added "2024-07-11T173617.685+00:00" The part for timezone but its still not working :/

Francisco Antunes

09/10/2024, 7:14 PM

Hi Doug, I’m following up with our devs right now about this one. I’ll let you know as soon as we have more information about the interaction between Databricks and the time zones feature!

✅ 1

Francisco Antunes

09/12/2024, 4:40 PM

Hi @Doug Creighton, we’ve heard back from our devs. They confirm that the Timezone feature has been tested and works for DataBricks data sources - so whatever is failing is not caused by any incompatibility. It’s most likely something in how it was configured, which we should review for sure. I understand that it still does not work; How so? Are your reports failing in any way? Or is it just the timezone that doesn’t seem to be applying? Have you followed all the steps from Manage Time Zone Settings in detail?

Doug Creighton

09/12/2024, 5:28 PM

I think we are circling back to when we were checking before when I run a query on https://reporting.laivly.cloud/api/v1/entities/workspaces/{workspace_id}/workspaceSettings/ I get this response, so it seems set up correctly

Copy code

{
  "data": [
    {
      "id": "timezone-us-ny",
      "type": "workspaceSetting",
      "attributes": {
        "content": {
          "value": "America/New_York"
        },
        "type": "TIMEZONE"
      },
      "links": {
        "self": "<https://reporting.laivly.cloud/api/v1/entities/workspaces/{workspace_id}/workspaceSettings/timezone-us-ny>"
      },
      "meta": {
        "origin": {
          "originType": "NATIVE",
          "originId": "{workspace_id}"
        }
      }
    }
  ],
  "links": {
    "self": "",
    "next": ""
  }
}

Doug Creighton

09/12/2024, 5:31 PM

The reports are the same as our backend database, no timezone change

Francisco Antunes

09/12/2024, 5:38 PM

Thanks for confirming! Just doing my due diligence 🙂 Could I ask you to try one of the example queries from the Databricks documentation, to make sure that the Timezone is indeed being applied on the source data? The example is:

Copy code

SELECT current_timezone(), TIMESTAMP'2021-7-1T8:43:28UTC+3';

Can you apply it to one of the timestamp entries from the data source and check the response? It should be something like:

Copy code

America/Los_Angeles 2021-06-30 22:43:28

Doug Creighton

09/12/2024, 5:49 PM

@Francisco Antunes FYI all our timezones are set to +00:00 Yes it works

Doug Creighton

09/12/2024, 5:50 PM

For example

Francisco Antunes

09/12/2024, 5:56 PM

Could you run it against one of the actual datapoints from the table?

Doug Creighton

09/12/2024, 5:56 PM

But there is now UTC+3 so nothing changes I'll need to add a timezone to the timestamp

5 Views

Open in Slack

Previous Next