Known Issues for Event Stream Processor Studio

Learn about known issues and apply workarounds for ESP Studio.

Studio Issues
CR# Description
682543

Deleting the key column from a named schema does not update the CCL editor. The CCL editor shows the column as a primary key and the project does not compile successfully.

Inline schema does not cause this problem. Update the project in the CCL editor to compile successfully.

690176

When running example projects from the Learning perspective, the Stream View is empty for some streams.

If you are running a project in the Learning perspective and you are working with a small data set, work around this issue by changing the stream view pulsed subscribe interval value to 0.

Set the interval back to its default value of 1 before working with any other projects.

717372

The ESP input adapter is available in the Studio palette. The adapter is required for internal processing, but it is not a supported adapter.

If you want to connect to another Event Stream Processor project, use stream binding instead. For more information, see the Studio Users Guide.

735930

When you run the Monitor view, it shows the wrong value (transactions for monitoring period) instead of the Rows Processed (/sec).

To measure throughput accurately, use the esp_monitor command line utility.

736394

After you click Record to start recording data input to a project, and input some records, clicking Stop does not stop the data recording.

736463

When a project encounters a license check error at startup, the project (under the workspace in the Server view) hangs while displaying the message project_name < ...connecting... >.

The workaround is to disconnect from the server and reconnect, then remove the project.