public class DBColumnRenameNodeModel extends DBNodeModel
|Modifier and Type||Field and Description|
Config identifier for the NodeSettings object contained in the NodeSettings which contains the settings.
|Modifier||Constructor and Description|
Constructor for the node model.
|Modifier and Type||Method and Description|
Configure method for general port types.
Execute method for general port types.
Sets new settings from the passed object in the model.
Adds to the given
Validates the settings in the passed
createDBQueryConnection, loadInternals, reset, saveInternals
addWarningListener, computeFinalOutputSpecs, configure, continueLoop, createInitialStreamableOperatorInternals, createMergeOperator, createStreamableOperator, execute, finishStreamableExecution, getAvailableFlowVariables, getAvailableInputFlowVariables, getCredentialsProvider, getInHiLiteHandler, getInPortType, getInputPortRoles, getInteractiveNodeView, getLogger, getLoopEndNode, getLoopStartNode, getNrInPorts, getNrOutPorts, getOutHiLiteHandler, getOutPortType, getOutputPortRoles, getWarningMessage, iterate, notifyViews, notifyWarningListeners, onDispose, peekFlowVariableDouble, peekFlowVariableInt, peekFlowVariableString, pushFlowVariableDouble, pushFlowVariableInt, pushFlowVariableString, removeWarningListener, resetAndConfigureLoopBody, setInHiLiteHandler, setWarningMessage, stateChanged
protected PortObjectSpec configure(PortObjectSpec inSpecs) throws InvalidSettingsException
PortObjectSpecsthat are defined through the
PortTypesgiven in the
constructorunless this model is an
InactiveBranchConsumer(most nodes are not). Similarly, the returned output specs need to comply with their port types spec class (otherwise an error is reported by the framework). They may also be null (out spec not known at time of configuration) or inactive (output and downstream nodes are inactive).
For a general description of the configure method refer to the description of the specialized
NodeModel.configure(DataTableSpec) methods as it addresses more use cases.
inSpecs- The input data table specs. Items of the array could be null if no spec is available from the corresponding input port (i.e. not connected or upstream node does not produce an output spec). If a port is of type
BufferedDataTable.TYPEand no spec is available the framework will replace null by an empty
DataTableSpec(no columns) unless the port is marked as optional as per constructor.
InvalidSettingsException- If this node can't be configured.
protected PortObject execute(PortObject inObjects, ExecutionContext exec) throws Exception
inObjectsrepresent the input objects and the returned array represents the output objects. The elements in the argument array are generally guaranteed to be not null and subclasses of the
PortObject classesthat are defined through the
PortTypesgiven in the
constructor. Similarly, the returned output objects need to comply with their port types object class (otherwise an error is reported by the framework) and must not be null. There are few exceptions to these rules:
InactiveBranchConsumermay find instances of
InactiveBranchPortObjectin case the corresponding input is inactive.
InactiveBranchPortObjectelements in case the output should be inactivated.
For a general description of the execute method refer to the description of the specialized
NodeModel.execute(BufferedDataTable, ExecutionContext) methods as it addresses more use cases.
protected void saveSettingsTo(NodeSettingsWO settings)
NodeSettingsthe model specific settings. The settings don't need to be complete or consistent. If, right after startup, no valid settings are available this method can write either nothing or invalid settings.
Method is called by the
Node if the current settings need
to be saved or transfered to the node's dialog.
settings- The object to write settings into.
protected void validateSettings(NodeSettingsRO settings) throws InvalidSettingsException
NodeSettingsobject. The specified settings should be checked for completeness and consistency. It must be possible to load a settings object validated here without any exception in the
#loadValidatedSettings(NodeSettings)method. The method must not change the current settings in the model - it is supposed to just check them. If some settings are missing, invalid, inconsistent, or just not right throw an exception with a message useful to the user.
settings- The settings to validate.
InvalidSettingsException- If the validation of the settings failed.
protected void loadValidatedSettingsFrom(NodeSettingsRO settings) throws InvalidSettingsException
#validateSettings(NodeSettings)method. The model must set its internal configuration according to the settings object passed.
KNIME GmbH, Konstanz, Germany
You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, display, or in any way exploit any of the content, in whole or in part, except as otherwise expressly permitted in writing by the copyright owner or as specified in the license file distributed with this product.