Skip to content

Add assert#12966

Closed
nanditajayanthi wants to merge 73 commits intoapache:masterfrom
nanditajayanthi:add_assert
Closed

Add assert#12966
nanditajayanthi wants to merge 73 commits intoapache:masterfrom
nanditajayanthi:add_assert

Conversation

@nanditajayanthi
Copy link
Copy Markdown
Contributor

Added assert statements to testParquetFile(String filePath) to ensure that test fails/passes are noted correctly
#12965

@nanditajayanthi nanditajayanthi marked this pull request as draft April 18, 2024 21:47
* upgrade maven-shade-plugin to 3.5.2

* Remove build-shade jar profile
File dataFile = new File(URLDecoder.decode(getClass().getClassLoader().getResource(filePath).getFile(), "UTF-8"));
ParquetNativeRecordReader recordReader = new ParquetNativeRecordReader();
recordReader.init(dataFile, null, null);
int counter = 0;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would it be more explicit if we count numDocsForFirstPass and numDocsForSecondPass and compare them? Can you also use try-with-resource to close the record reader (not introduced in this PR)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

For this PR, I can count numDocsForFirstPass and numDocsForSecondPass explicitly. This PR is mainly intended to add an assertion mechanism. Is it still necessary to use the try-with-resource in this PR?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

E.g when the assert fails, it will leak resource because the last close() won't be executed. Using try-with-resource is just good practice to prevent resource leak

@Jackie-Jiang Jackie-Jiang added the testing Related to tests or test infrastructure label Apr 18, 2024
deemoliu and others added 24 commits April 18, 2024 15:54
…hem (apache#12883)

* skip missing segments while checking freshness during server startup

* get new consuming segments again if current consuming segments are committed by other servers
dependabot bot and others added 28 commits April 29, 2024 11:04
Created new Action GET_SCHEDULER_JOB_DETAILS  under the Table actions for the endpoint /tasks/scheduler/jobDetails as its fetching table level information and the existing action puts this endpoint under Cluster actions.
Change the multi-stage stats to return a tree like structure with stats per operator.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing Related to tests or test infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.