Data view editor plugin uses Rollup Jobs internal API endpoint

[yuliacech]

The Data view editor plugin relies on an internal API endpoint of the Rollup Jobs plugin (see here).

 private getRollupIndexCaps = async () => {
    let rollupIndicesCaps: RollupIndicesCapsResponse = {};
    try {
      rollupIndicesCaps = await this.http.get<RollupIndicesCapsResponse>('/api/rollup/indices');
    } catch (e) {
      // Silently swallow failure responses such as expired trials
    }
    this.updateState({ rollupIndicesCaps });
    return rollupIndicesCaps;
  };

The API endpoint /api/rollup/indices is only intended for internal use by the Rollup jobs plugin's client-side. Since the dependency via API usage is not explicit, any changes to the API endpoint might not be immediately propagated to the dependent plugins. The plugin is also planned to be disabled for serverless.

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[mattkime]

@yuliacech I could use your advice figuring out how to move forward on this. Data views code needs a way to get a list of rollup indices. Perhaps the rollup jobs plugin should make such functionality available on its plugin contract.

I also need to do a deeper inventory of data view related code to see where we're we have rollup specific code.

Has anything been said about how rollup data might be migrated? I guess I'm not really expecting an answer on that, but I do need to think of how I might handle data views defined on a rollup index.

[yuliacech]

Hi @mattkime, thanks a lot for looking into this.
We are currently not actively working on the rollup jobs plugin (because downsampling seems to be the better alternative to rollups), so I'm not sure if we will be able to add the list functionality to the plugins contract. So instead to get a list of rollup indices you could directly call the ES API for rollup index caps (see here) in the data views plugin.
What did you mean by "how rollup data might be migrated"?

[mattkime]

@yuliacech

What did you mean by "how rollup data might be migrated"?

Whats the user story regarding migration to the cloud? What happens if they attempt to migrate rollup data and saved objects? What happens if someone individually exports a rollup data view and imports it in an environment without rollup support?

[kertal]

@mattkime @yuliacech could you follow up here so we can identify if there's stuff to do for 8.9. For me the main question is, what happens if a user imports a rollup data view in an environment without rollup support? This could be already tested, by disabling the rollup plugin

[mattkime]

@kertal We need to investigate this and define what we would like to happen. No thought has been put into user experience.

[yuliacech]

what happens if a user imports a rollup data view in an environment without rollup support?

@shubhaat could you please help answer this question?

[shubhaat]

• @ninoslavmiskovic - Can you take a look at this?

[yuliacech]

I think there is also a section in Advanced setting related to this