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

Match the CA attribute with the Elaticsearch attribute #30411

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

Match the CA attribute with the Elaticsearch attribute #30411

freddyDOTCMS opened this issue Oct 18, 2024 · 0 comments

Comments

@freddyDOTCMS
Copy link
Contributor

Parent Issue

No response

Problem Statement

Right now the CA attribute are totally different from what we used in ES, for example, the Contentlet's ID is saved as "identifier" , we used: contentId, also we have others fields that have the same value like : pageId, fileId, vanityId, the only different is that this attribute are NULL when is not the right type on Contentlet, for example pageId is NULL is the COntentlet is a Image.

Also we are not saving some values that we need like the ContentType variable Name, or the Base Content Type, the list of attribute that we want to match with ES are:

Attribute that already exists in CA but we need to rename:

  • contentId - > identifier
  • contenTitle -> title
  • urlMapContentTypeVarName -> contentType
  • renderMode -> turn into to boolean live and working
  • language -> languageId
  • host -> conHost
  • vanityForwardTo -> fowardTo
  • vanityResponse -> action
  • urlMapWasHit and wasVanityHit -> Join in just one attribute that tell if Vanity or URL MAP was used

We need to removed some attribute too like:

  • isDetailPage
  • urlMapContentDetailId
  • urlMapContentDetailTitle
  • urlMapContentId
  • urlMapContentTypeName
  • urlMapContentTypeVarName

Also we need to include some attribute that we are not collecting right now:

  • baseType
  • Path

Steps to Reproduce

Start Analytics generate some CA data
Go to CubeJS Server and check the field names

Acceptance Criteria

We need to rename, removed and create the fields describe before

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