Refresh Schema bugfix

Tim · ‎09-23-2024

See here: https://community.sisense.com/t5/technical-troubleshooting/refresh-schema-error/m-p/23594#M195 Refresh Schema fails when you have tables from two different schemas.

gupta3 · ‎02-27-2024

Standard Live and Elasticube connector for AWS EMR: https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-connectors.html

lsher1 · ‎02-15-2024

When creating a new table in an Elasticube, the area to write code into takes up a fraction of the screen space. Please make the pop-up to write code for tables stretch across the whole screen so users can see more lines of code at once. Or make the pop-up window adjustable so we can move it to be as big as we like.

fschleich · ‎09-15-2023

Hello, How about having a better control over queries parallelism ? My use case : Elasticubes using 2 connections : DB1 / DB2 Currently, the parameter BaseTableMaxThreads (sets to 2 for us) controls how many queries can run in parallel, whatever the connection. During build, we frequently see situations where we have 1 query on DB1 and another one on DB2. Reducing the level of parallelism was necessary to limit contention on one connection but it would be fine to have 2 queries on DB1 and 2 queries on DB2 at the same time. My proposal is the following : having a parameters to controls the level of parallelism per connection and not per build. Thank you.

Sisense Community

Refresh Schema bugfix

AWS EMR Connector

Elasticube SQL Area

Elacticube build - Level of parallelism