Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate storing Exception for stack trace rather than using Strings #361

Closed
philwebb opened this issue Jan 12, 2017 · 3 comments
Closed
Labels
type/enhancement A general enhancement
Milestone

Comments

@philwebb
Copy link

Currently the operatorStacktrace stores a String copy of the stack trace. It might be quicker to instead store Exception instances and only use printStackTrace if absolutely necessary.

@philwebb
Copy link
Author

See SPR-14944 for background.

@smaldini smaldini added the type/enhancement A general enhancement label Jan 12, 2017
@smaldini smaldini added this to the 3.0.5.RELEASE milestone Jan 12, 2017
smaldini pushed a commit that referenced this issue Jan 12, 2017
@smaldini
Copy link
Contributor

smaldini commented Jan 12, 2017

@philwebb if you have a mean to test the 3.0.5.BUILD-SNAPSHOT, please let me know (building now, avail in 3mn)

@smaldini
Copy link
Contributor

Will keep under this form for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants