automatic incremental statement naming

[DevDrake]

automatic incremental statement naming

[bernhardttom]

Check under DeploymentOptions there is a StatementNameRuntimeOption that sets the statement name

[DevDrake]

Thanks

It looks that providing something like

public static class StatementNameRuntimeOptionImpl implements StatementNameRuntimeOption {
    @Override
    public String getStatementName(final StatementNameRuntimeContext statementNameRuntimeContext) {
        return "stmt-" + statementNameRuntimeContext.getStatementId();
    }
}

gives similar results to esper pre 8.

Then looking at statementId that is incremented for every deployment, does it mean that statementName being mostly stmt-0 (for not named statements) is a bug ?
For me it looks that way.

To have it behaves automatically with having option of using @name() we need to use string comparison of some kind with "guessed" automatic name like "stmt-0" doesn't seems perfect. It also look that it may behaves slight different when statement is partitioned.

[bernhardttom]

In Esper 8 the combination of deployment id and statement name identifies each statement in a runtime

[DevDrake]

What a significance statementId does have then ?
Source of my confusion is that the statementId is disconnected from default statementName.

Custom naming works ok, but it's quiet strange how it is working internally. First @name or default name is applied and then as an option it can be overridden. The problem here is StatementNameRuntimeContext hasn't information what kind of name was provided to the statement (default or from @name).