pentaho/pentaho-kettle · error · KettleException
Invalid '' '' with '' ''. See Palo documentation.
Error message
Invalid {0} ''{1}'' with {2} ''{3}''. See Palo documentation. What it means
PaloCellOutputDialog.getInfo() rejects an invalid combination of the step's update mode and splash mode. Parameterized message 'Invalid {0} ''{1}'' with {2} ''{3}''. See Palo documentation.' is thrown when update mode resolves to 'ADD' while splash mode resolves to 'SET' — a combination the Palo server API does not allow, so the dialog fails while saving settings via OK (ok -> getInfo).
Solutions
- Change the splash mode to something other than SET, or the update mode to something other than ADD.
- Consult the Palo documentation for valid update/splash mode combinations.
- If SET-splash behavior is required, restructure the step or use a different update mode.
Example fix
// before
comboUpdateMode.setText("ADD");
comboSplashMode.setText("SET"); // invalid combination
// after
comboUpdateMode.setText("ADD");
comboSplashMode.setText("DEFAULT"); // splash not allowed with ADD Defensive patterns
Strategy: validation
Validate before calling
boolean invalid = "ADD".equals(updateMode) && "SET".equals(splashMode);
if (invalid) { /* change splash mode or update mode before saving */ } Prevention
- Never combine update mode ADD with splash mode SET.
- Document valid update/splash combinations for your team.
- Standardize dialog defaults that are known-valid.
When it happens
Trigger: Pressing OK in the Palo Cell Output dialog while the Update combo is set to ADD and the Splash combo is set to SET.
Common situations: User selects splash mode SET (which writes/splashes a whole cube area) while update mode ADD is selected, not realizing PALO forbids splashing with ADD; defaults from an older transformation template.
Understand the failure class
Background: Conflicting config options: "cannot be used together" — configuration validation errors across open-source libraries — this error's family across 162 libraries.
Related errors
- A connection of type PALO is expected
- A connection of type PALO is expected
- All fields must have an output type to do the preview
- Commit size must be an integer.
- Failed to add Cell Row:
AI-assisted analysis of pentaho/pentaho-kettle@f3058517a1 (2026-09-13).
Data as JSON: /api/errors/54bec281b7eb5344.
Report an issue: GitHub.
Appendix: source
Thrown at plugins/palo/core/src/main/java/org/pentaho/di/ui/trans/steps/palo/celloutput/PaloCellOutputDialog.java:621
try {
getInfo( this.meta );
dispose();
} catch ( KettleException e ) {
new ErrorDialog(
shell,
BaseMessages.getString( PKG, "PaloCellOutputDialog.FailedToSaveDataErrorTitle" ),
BaseMessages.getString( PKG, "PaloCellOutputDialog.FailedToSaveDataError" ),
e );
}
}
private void getInfo( PaloCellOutputMeta myMeta ) throws KettleException {
stepname = textStepName.getText();
List<DimensionField> fields = new ArrayList<DimensionField>();
if ( this.updateOptions.getCode( comboUpdateMode.getText() ) == "ADD"
&& this.splashOptions.getCode( comboSplashMode.getText() ) == "SET" ) {
throw new KettleException(
BaseMessages.getString( PKG, "PaloCellOutputDialog.UpdateSplashError",
BaseMessages.getString( PKG, "PaloCellOutputDialog.UpdateMode" ),
comboUpdateMode.getText(),
BaseMessages.getString( PKG, "PaloCellOutputDialog.SplashMode" ),
comboSplashMode.getText()
)
);
}
try {
Integer.parseInt( this.textCommitSize.getText() );
} catch ( Exception e ) {
throw new KettleException( BaseMessages.getString( PKG, "PaloCellOutputDialog.CommitSizeErrorMessage" ) );
}
for ( int i = 0; i < tableViewFields.table.getItemCount(); i++ ) {
DimensionField field =View on GitHub (pinned to f3058517a1)