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

Need support date a specific date range in our Query sintax #30410

Open
freddyDOTCMS opened this issue Oct 18, 2024 · 0 comments
Open

Need support date a specific date range in our Query sintax #30410

freddyDOTCMS opened this issue Oct 18, 2024 · 0 comments

Comments

@freddyDOTCMS
Copy link
Contributor

Parent Issue

No response

Problem Statement

CubeJS Query allow to set a specific range of date like in this query:


{
  "measures": [
    "request.count"
  ],
  "dimensions": [
    "request.contentletId",
    "request.contentletTitle",
    "request.whatAmI",
    "request.url"
  ],
  "order": {
    "request.count": "desc"
  },
  "timeDimensions": [
    {
      "dimension": "request.createdAt",
      "granularity": "day",
      "dateRange": [
        "2024-10-07T06:00:00",
        "2024-10-20T05:59:59.999"
      ]
    }
  ]
}

right now we are supporting friendly range date like 'last month' but not a specific range date, the reasons is because they are translate to CubeJs in a complete different way, a friendly range is tranlate like:


  "timeDimensions": [
    {
      "dimension": "request.createdAt",
      "granularity": "second",
      "dateRange": "This month"
    }
  ],

Steps to Reproduce

Try to run a query using the '/v1/analytics/content/_query' Endpoint using a specific range of dates

Acceptance Criteria

Must support this kind of range of date

dotCMS Version

latest

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Next 1-3 Sprints
Development

No branches or pull requests

1 participant