We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Current behaviour:
/user/myuser/myservice//myentityId_myentityType/myentityId_myentityType.txt
myservice
_myentityId_myentityType
myentityId_myentityType
sth_myservice
sth_/_myentityId_myentityType
myservice__myentityId_myentityType
In addition, subsvc field in log4j logs is empty when / is notified (or configured as default).
subsvc
/
Do we accept this default behaviour? Alternatives?
My proposal:
//
_
__
The text was updated successfully, but these errors were encountered:
This must be applied both to release/0.13.0 and release/0.14.0
Sorry, something went wrong.
LGTM
Implemented in PR #883 and PR #896 (develop branch) Implemented in PR #886 and PR #897 (release/0.13.0 branch)
frbattid
No branches or pull requests
Current behaviour:
/user/myuser/myservice//myentityId_myentityType/myentityId_myentityType.txt
myservice
, table_myentityId_myentityType
myservice
, pkgNamemyservice
, resNamemyentityId_myentityType
sth_myservice
, collectionsth_/_myentityId_myentityType
myservice__myentityId_myentityType
myservice
, table_myentityId_myentityType
In addition,
subsvc
field in log4j logs is empty when/
is notified (or configured as default).Do we accept this default behaviour? Alternatives?
My proposal:
/
instead of//
_
_
instead of__
_
The text was updated successfully, but these errors were encountered: