Skip to content

(bug): fix magic accidentally overriding RumbleDB parameters - #45

Open
McLavish wants to merge 2 commits into
RumbleDB:mainfrom
McLavish:fix/remove-rumbledb-init
Open

(bug): fix magic accidentally overriding RumbleDB parameters#45
McLavish wants to merge 2 commits into
RumbleDB:mainfrom
McLavish:fix/remove-rumbledb-init

Conversation

@McLavish

Copy link
Copy Markdown

Expected behavior

If the user has specified a RumbleDB instance in their notebook, the magic should not override the user configuration.

Current behavior

%load_ext jsoniqmagic instantiates a default RumbleSession itself. If the user runs it before a Spark/RumbleDB setup cell, the JVM is created with default parameters and options like spark.driver.memory=4g are ignored. Spark runs with a 1 GiB heap instead of 4 GiB.

Example 1:

image image

Description:

The %load_ext jsoniqmagic overrides the user configuration. Spark is instantiated with the incorrect memory and shuffle partitions.

Example 2:

image image

Description:

In this case %load_ext jsoniqmagic does not override the RumbleSession memory and shuffle partitions configuration. However, it overrides the setResultSizeCap configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant