Skip to content

CSV-285: Replace BufferedReader with PushbackReader#169

Closed
belugabehr wants to merge 1 commit into
apache:masterfrom
belugabehr:CSV-285
Closed

CSV-285: Replace BufferedReader with PushbackReader#169
belugabehr wants to merge 1 commit into
apache:masterfrom
belugabehr:CSV-285

Conversation

@belugabehr

Copy link
Copy Markdown
Contributor

@belugabehr

belugabehr commented Jul 16, 2021

Copy link
Copy Markdown
Contributor Author

Hold off on this one for right now, the JMH tests are not as favorable as I was expecting. I need to review the tests.

@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.3%) to 97.99% when pulling 532a3f1 on belugabehr:CSV-285 into 27843d8 on apache:master.

@garydgregory

Copy link
Copy Markdown
Member

No rush. I might cut a release candidate next week or so but this is a major change we might only want to do after that.

@belugabehr

Copy link
Copy Markdown
Contributor Author

Ya, all the unit tests pass, but I definitely see some flaws in my attempt here. Do not commit.

@belugabehr

Copy link
Copy Markdown
Contributor Author

@garydgregory

Weird timing that I just happened to pick up CSV commons work the other day. I thought I was making big progress on performance, but my research just revealed that there was a big performance regression as part of adding support for String delimiters #76 which was just added to master recently. My contributions this week made some incremental improvements, but really the big performance improvement I addressed in #167 which bypasses the work in #76 by short-circuiting for the common use case of a single delimiter character. With #167 in place, the performance is much more similar to the current 1.8 version and not nearly as impressive as I had thought.

@garydgregory

Copy link
Copy Markdown
Member

Hi @belugabehr,
Please note that I merged a bug fix today related to string delimiters.

@garydgregory

Copy link
Copy Markdown
Member

Hi @belugabehr
Are you still working on this PR or should it be closed?

@belugabehr

Copy link
Copy Markdown
Contributor Author

I'm going to close this.

I think a push-back buffer is cleaner as it's really well suited for this use case, but the current implementation is faster (and not all that hard to follow).

@belugabehr belugabehr closed this Oct 15, 2022
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.

3 participants