-
Notifications
You must be signed in to change notification settings - Fork 12
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
use MetaStorage.get where null allowed #3630
Conversation
…ectColumnValuesJob (#3618) * adds soft pool cleaner, configuration and allocation limiter for CollectColumnValuesJob * use 4 kibibytes as default chunk size for NetworkSession * Reduce queue size of NetworkSession and make configurable. --------- Co-authored-by: awildturtok <[email protected]>
e9d3b4d
to
5f2553c
Compare
It is a potentially excepting operation which may cause the entire stack to crash. Instead use *Storage.get which will produce null. Handling is then at the discretion of the caller.
5f2553c
to
c1dad12
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sehr cool, dass du noch einige abkürzungen gefunden hast!
backend/src/main/java/com/bakdata/conquery/io/result/excel/ExcelRenderer.java
Outdated
Show resolved
Hide resolved
@@ -57,6 +57,7 @@ public CDateRange getValidityDate(int event, Bucket bucket) { | |||
// JsonCreator was not happy, and I could not figure out why. This is probably the most performant implementation that's not two classes. | |||
|
|||
if (getColumn() != null) { | |||
// TODO resolve in hot loop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Vielleicht im Konstruktor schon zu transient resolven, dann passiert das resolven nur einmal beim laden des Concepts
status.setOwner(user.getId()); | ||
status.setOwnerName(user.getLabel()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sollten wir noch checken: Was macht das Frontend, wenn die null sind
@thoniTUB ich hatte gehofft die initaliisierung über initializer zu machen, aber da läuft es in Probleme, weil wir im LoadingUtil Konzepte mit FailingProviders laden und dann knallt es im resolven. Das ist erstmal eine zwischen Lösung. (Ich werde vermutlich einmal in die Ids eingreifen müssen, jetzt wo ich mehr gesehen habe wie es funktioniert und wo es hakt) |
if (extractor == null){ | ||
//TODO this is just a workaround: We should actually be using Initializing, which sadly gives us issues with LoadingUtil | ||
init(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ja das mit der Abhängigkeit hatte ich in den Tests nicht beachtet. Sehe aber auch keine besser Lösung
No description provided.