这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@its-colby
Copy link

@its-colby its-colby commented Jul 16, 2021

This is added support for the WebUI. It supports previous functionality of a much older version of Tuplex as well as new support for splitting the plan into stages, tracking stage dependencies, join operators, aggregate operators, and showing UDF's for filter operators.

It would be great if you could do a code review and tell me what I should change.

numOutputRows += task->getNumOutputRows();
}
} else {
auto rs = tstage->resultSet();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this "consume" the resultset?

Copy link
Author

@its-colby its-colby Jul 18, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not exactly sure what you mean by "consume".

// delete task
delete tasks[i];
tasks[i] = nullptr;
// delete tasks[i];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this commented? bug?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is commented because it was leading to a bug. This delete was added during the open sourcing, as it was not on my old branch in the old repo. The bug was the following: executeTransformStage calls createFinalHashmap. createFinalHashmap ends up deleting the tasks. Later in executeTransformStage, if the webUI is enabled, we have to iterate through the tasks to get the number of output rows. However, this was causing a nullptr dereference. So I commented the delete tasks[I] and setting it to a nullptr. If the memory is not being managed elsewhere, the tasks can be deleted after the history server is done using them and then deleted in an else statement if webUI not enabled.

@its-colby
Copy link
Author

Note: Before merging to master, I would like to write some of my own comprehensive tests to ensure everything is working. Basically using the history server to look at complex pipelines with many error rows.

Copy link
Contributor

@LeonhardFS LeonhardFS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you go over the comments? we probably should also do a functional test and check that the HTML/JS works well.

Great work so far getting this back working! Excited to have it shipped soon in future release 0.3.3.

@LeonhardFS
Copy link
Contributor

superseded by #38

@LeonhardFS LeonhardFS closed this Nov 3, 2021
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