Skip to content

fix(engine): the events of a trace are read from <Events> - #82

Merged
stbischof merged 1 commit into
eclipse-daanse:mainfrom
dbulahov:main201026_1
Oct 20, 2026
Merged

stbischof merged 1 commit into
eclipse-daanse:mainfrom
dbulahov:main201026_1

Conversation

@dbulahov

Copy link
Copy Markdown
Contributor

What does this PR do?

AMO writes a trace's events as <Events><Event>…</Event></Events>: the property is Microsoft.AnalysisServices.Trace.Events, an [XmlArray] without a name of its own (AMO 19.114.12, Trace.cs), and ASSL names the element the same way. The engine model called the element of the Trace.eventType reference EventType, so the reader skipped <Events>, and a trace from SQL Server Profiler or SSMS arrived without a single event.

The change is one line in model/engine/model/engine.ecore: the ExtendedMetaData name of Trace.eventType is Events instead of EventType. The class EventType, its Event children and the Java names (getEventType()) stay as they are.

AMO writes a trace's events as <Events><Event>…</Event></Events> (Microsoft.AnalysisServices.Trace.Events, an
[XmlArray] without a name), as ASSL names them; the model read them as <EventType>, so a trace from SQL Server
Profiler or SSMS arrived without an event.

Signed-off-by: dbulahov <bulahovdenis@gmail.com>
@sonarqubecloud

Copy link
Copy Markdown

@stbischof
stbischof merged commit a5e938b into eclipse-daanse:main Oct 20, 2026
24 checks passed
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.

2 participants