[jira] [Commented] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865822#comment-17865822
]
Sercan Tekin commented on RANGER-4225:
--
Thank you [~madhan] and [~bpatel] for your help with this ticket.
Should also close https://issues.apache.org/jira/browse/RANGER-3409?
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Fix For: 3.0.0, 2.5.0
>
> Attachments: RANGER-4225-2.patch, RANGER-4225-3.patch,
> RANGER-4225.patch
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> +*PROBLEM:*+
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class, and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger v2.4.0;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings instead:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below error while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> +*REFERENCES:*+
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> +*SOLUTION:*+
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> The PR is attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3409) Update Jackson and remove Codehaus version
[
https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848223#comment-17848223
]
Sercan Tekin edited comment on RANGER-3409 at 5/21/24 2:32 PM:
---
[~bpatel], you're correct. My intention was only to address the camel-case
conflict in the first place.
But now, I've incorporated [~n.blagodarny]'s solution (crediting as the
author), and then cherry-picked the solution for the conflict on top of it in
my PR.
Could you folks please review and test this now? ->
https://github.com/apache/ranger/pull/252
PS: [~n.blagodarny], have you changed your user name or email address in your
git account> None of the below options link you as an author to your github
account:
{code:java}
git commit --amend --author="Nikita Blagodarnyi "
git commit --amend --author="nblagodarnyi "
git commit --amend --author="n.blagodarny "
{code}
Even in your own PR, in the commit details, your name is not linked to your
account.
was (Author: JIRAUSER283532):
[~bpatel], you're correct. My intention was only to address the camel-case
conflict in the first place.
But now, I've incorporated [~n.blagodarny]'s solution (crediting as the
author), and then cherry-picked the solution for the conflict on top of it in
my PR.
Could you folks please review and test this now? ->
https://github.com/apache/ranger/pull/252
> Update Jackson and remove Codehaus version
> --
>
> Key: RANGER-3409
> URL: https://issues.apache.org/jira/browse/RANGER-3409
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Andrew Charneski
>Priority: Blocker
> Attachments: ranger-modify-policy.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> An old version of Jackson (Codehaus Jackson 1.9.13) is still being used.
> Jackson has since moved namespaces with a reorganized library structure.
> Update all references to the older version to use the newer version (which is
> currently used in some modules).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848223#comment-17848223 ] Sercan Tekin edited comment on RANGER-3409 at 5/21/24 2:26 PM: --- [~bpatel], you're correct. My intention was only to address the camel-case conflict in the first place. But now, I've incorporated [~n.blagodarny]'s solution (crediting as the author), and then cherry-picked the solution for the conflict on top of it in my PR. Could you folks please review and test this now? -> https://github.com/apache/ranger/pull/252 was (Author: JIRAUSER283532): [~bpatel], you're correct. My intention was only to address the camel-case conflict in the first place. But now, I've incorporated [~n.blagodarny]'s solution (crediting as the author), and then cherry-picked the solution for the conflict on top of it in my PR. Could you folks review and test this now? -> https://github.com/apache/ranger/pull/252 > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Attachments: ranger-modify-policy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848223#comment-17848223 ] Sercan Tekin commented on RANGER-3409: -- [~bpatel], you're correct. My intention was only to address the camel-case conflict in the first place. But now, I've incorporated [~n.blagodarny]'s solution (crediting as the author), and then cherry-picked the solution for the conflict on top of it in my PR. Could you folks review and test this now? -> https://github.com/apache/ranger/pull/252 > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Attachments: ranger-modify-policy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846939#comment-17846939 ] Sercan Tekin commented on RANGER-3409: -- [~n.blagodarny], I believe checking the policy editing/creating page will be sufficient in this case. Could you please try adding a user to a policy? I am not sure how your usersync is configured, but I think you will not be able to see system/LDAP users in the drop-down menu. Here is an old UI screenshot for reference. When I encountered this issue, I noticed that no users were available to add: !ranger-modify-policy.png! During debugging, I found that while the functionality was intact, Jackson was unable to detect Java Bean class properties due to a camel case naming issue. > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Attachments: ranger-modify-policy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sercan Tekin updated RANGER-3409: - Attachment: ranger-modify-policy.png > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Attachments: ranger-modify-policy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846596#comment-17846596 ] Sercan Tekin commented on RANGER-3409: -- [~bpatel], this is what I described and proposed solution in https://issues.apache.org/jira/browse/RANGER-4225. Issue -> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c] Solution -> [https://github.com/apache/ranger/pull/252] FYI > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806104#comment-17806104
]
Sercan Tekin commented on RANGER-4225:
--
[~bpatel], sure! Working on it, I will share the details and how I test the
patch here
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4225.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> +*PROBLEM:*+
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class, and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger v2.4.0;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings instead:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below error while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> +*REFERENCES:*+
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> +*SOLUTION:*+
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> The PR is attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803551#comment-17803551 ] Sercan Tekin commented on RANGER-3409: -- Please be aware of this Jira https://issues.apache.org/jira/browse/RANGER-4225. Upgrading to Jackson-2 will cause the issue described in there > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774113#comment-17774113
]
Sercan Tekin commented on RANGER-4225:
--
Created review request https://reviews.apache.org/r/74662/
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4225.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> +*PROBLEM:*+
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class, and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger v2.4.0;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings instead:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below error while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> +*REFERENCES:*+
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> +*SOLUTION:*+
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> The PR is attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
+*PROBLEM:*+
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env and conflicted with Jackson-1 dependencies.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class, and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger
v2.4.0;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings instead:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below error while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
+*REFERENCES:*+
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
+*SOLUTION:*+
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
The PR is attached.
was:
*PROBLEM:*
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env and conflicted with Jackson-1 dependencies.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/wh
[jira] [Updated] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Fix Version/s: 3.0.0
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4225.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *PROBLEM:*
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Affects Version/s: 2.4.0
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Attachments: RANGER-4225.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *PROBLEM:*
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Attachment: RANGER-4225.patch
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Attachments: RANGER-4225.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *PROBLEM:*
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Summary: Possible Jackson serialization issue due to not comply with Java
bean standards (was: Possible Jackson serialization issue due to not comply to
Java bean standards)
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *PROBLEM:*
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization issue due to not comply to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Summary: Possible Jackson serialization issue due to not comply to Java
bean standards (was: Possible Jackson serialization issue due to not complain
to Java bean standards)
> Possible Jackson serialization issue due to not comply to Java bean standards
> -
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *PROBLEM:*
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization issue due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Summary: Possible Jackson serialization issue due to not complain to Java
bean standards (was: Possible Jackson serialization due to not complain to
Java bean standards)
> Possible Jackson serialization issue due to not complain to Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *PROBLEM:*
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin reassigned RANGER-4225:
Assignee: Sercan Tekin
> Possible Jackson serialization due to not complain to Java bean standards
> -
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *PROBLEM:*
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
*PROBLEM:*
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env and conflicted with Jackson-1 dependencies.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
was:
*PROBLEM:*
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if
[jira] [Updated] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
*PROBLEM:*
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
was:
*PROBLEM*
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@J
[jira] [Updated] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
*PROBLEM*
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
was:
{*}PROBLEM:{*}{*}{*}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTI
[jira] [Updated] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
{*}PROBLEM:{*}{*}{*}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
was:
{*}PROBLEM:{*}{*}{{*}}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-
[jira] [Updated] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
{*}PROBLEM:{*}{*}{{*}}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger's model classes don't comply with the
convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
was:
{*}PROBLEM:{*}{*}{*}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger classes don't comply with the convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SO
[jira] [Updated] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
{*}PROBLEM:{*}{*}{*}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger classes don't comply with the convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
was:
{*}PROBLEM:{*}{*}{{*}}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger classes don't comply with the convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
[jira] [Commented] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719582#comment-17719582
]
Sercan Tekin commented on RANGER-4225:
--
Please see PR [https://github.com/apache/ranger/pull/252]
> Possible Jackson serialization due to not complain to Java bean standards
> -
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sercan Tekin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {*}PROBLEM:{*}{*}{{*}}
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class and some of the Ranger classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below issue while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> *REFERENCES:*
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> *SOLUTION:*
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sercan Tekin updated RANGER-4225:
-
Description:
{*}PROBLEM:{*}{*}{{*}}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger classes don't comply with the convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
was:
{*}PROBLEM:{*}{*}{*}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger classes don't comply with the convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION
[jira] [Created] (RANGER-4225) Possible Jackson serialization due to not complain to Java bean standards
Sercan Tekin created RANGER-4225:
Summary: Possible Jackson serialization due to not complain to
Java bean standards
Key: RANGER-4225
URL: https://issues.apache.org/jira/browse/RANGER-4225
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Sercan Tekin
{*}PROBLEM:{*}{*}{*}
Transitive Jackson-2 dependencies are included into Ranger's classpath in my
env.
Jackson-2 uses Javabean naming conventions to figure out the Json properties in
a Java class and some of the Ranger classes don't comply with the convention.
For example, when the leading camelcase word is only one letter in length, then
deserialized response is broken. The following is what I observed in Ranger;
On Ranger UI side, this
[code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
attempts to read vXStrings key in map, but the corresponding response has
vxstrings:
{code:java}
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 11,
"resultSize": 11,
"sortType": "asc",
"sortBy": "id",
"listSize": 11,
"vxstrings": [< here! This has to be vXStrings
{
"value": "public",
... {code}
And this difference causes below issue while reading the property, therefore
the corresponding dropdown has no values as excepted;
{code:java}
PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
properties of undefined (reading 'map')
at Object.results (PermissionList.js?ver=build.version:226:34)
at Object.success (select2.js?ver=build.version:450:47)
at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
at Object.fireWith [as resolveWith]
(jquery-3.3.1.min.js?ver=build.version:2:28202)
at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
at XMLHttpRequest.
(jquery-3.3.1.min.js?ver=build.version:2:79907){code}
*REFERENCES:*
Please see this reference related to capital letters
[http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
"Don't capitalize first two letters of a bean property name. This is in our
java standards. You should not create a java bean property name that begins
with a capital letter in the 1st two places."
Also you can see the same issue is reported here
[https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
*SOLUTION:*
{{@JsonProperty}} annotation needs to be added for mapping the properties with
their corresponding getter/setter methods. This will not effect Ranger's
functionality directly, but it will provide consistency even if Jackson-2 is
included into classpath.
I have tested it locally after adding {{@JsonProperty}} and everything worked
well.
I will be providing a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
[ https://issues.apache.org/jira/browse/RANGER-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598792#comment-17598792 ] Sercan Tekin commented on RANGER-3894: -- To solve this issue, https://issues.apache.org/jira/browse/HIVE-21753 needs to be backported to Hive-3, and [this-block|https://github.com/apache/ranger/blob/master/hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java#L162-L171] needs to be uncommented. The result will be; !metastore.png! [~rmani], any chance to backport HIVE-21573 to Hive-3? > Application is 'unknown' for metastore in plugin status page > > > Key: RANGER-3894 > URL: https://issues.apache.org/jira/browse/RANGER-3894 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Sercan Tekin >Priority: Minor > Fix For: 3.0.0, 2.4.0 > > Attachments: metastore.png, unknown.png > > > After https://issues.apache.org/jira/browse/RANGER-768 I have configured hive > plugin for metastore. In plugin status page, application column shows > 'unknown' for metastore as in screen shot; > !unknown.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
[ https://issues.apache.org/jira/browse/RANGER-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sercan Tekin updated RANGER-3894: - Attachment: metastore.png > Application is 'unknown' for metastore in plugin status page > > > Key: RANGER-3894 > URL: https://issues.apache.org/jira/browse/RANGER-3894 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Sercan Tekin >Priority: Minor > Fix For: 3.0.0, 2.4.0 > > Attachments: metastore.png, unknown.png > > > After https://issues.apache.org/jira/browse/RANGER-768 I have configured hive > plugin for metastore. In plugin status page, application column shows > 'unknown' for metastore as in screen shot; > !unknown.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
[ https://issues.apache.org/jira/browse/RANGER-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sercan Tekin updated RANGER-3894: - Attachment: unknown.png > Application is 'unknown' for metastore in plugin status page > > > Key: RANGER-3894 > URL: https://issues.apache.org/jira/browse/RANGER-3894 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Sercan Tekin >Priority: Minor > Fix For: 3.0.0, 2.4.0 > > Attachments: unknown.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
[ https://issues.apache.org/jira/browse/RANGER-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sercan Tekin updated RANGER-3894: - Description: After https://issues.apache.org/jira/browse/RANGER-768 I have configured hive plugin for metastore. In plugin status page, application column shows 'unknown' for metastore as in screen shot; !unknown.png! > Application is 'unknown' for metastore in plugin status page > > > Key: RANGER-3894 > URL: https://issues.apache.org/jira/browse/RANGER-3894 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Sercan Tekin >Priority: Minor > Fix For: 3.0.0, 2.4.0 > > Attachments: unknown.png > > > After https://issues.apache.org/jira/browse/RANGER-768 I have configured hive > plugin for metastore. In plugin status page, application column shows > 'unknown' for metastore as in screen shot; > !unknown.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
[ https://issues.apache.org/jira/browse/RANGER-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sercan Tekin updated RANGER-3894: - Attachment: (was: unknown.png) > Application is 'unknown' for metastore in plugin status page > > > Key: RANGER-3894 > URL: https://issues.apache.org/jira/browse/RANGER-3894 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Sercan Tekin >Priority: Minor > Fix For: 3.0.0, 2.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
[ https://issues.apache.org/jira/browse/RANGER-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sercan Tekin updated RANGER-3894: - Attachment: unknown.png > Application is 'unknown' for metastore in plugin status page > > > Key: RANGER-3894 > URL: https://issues.apache.org/jira/browse/RANGER-3894 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Sercan Tekin >Priority: Minor > Fix For: 3.0.0, 2.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
Sercan Tekin created RANGER-3894: Summary: Application is 'unknown' for metastore in plugin status page Key: RANGER-3894 URL: https://issues.apache.org/jira/browse/RANGER-3894 Project: Ranger Issue Type: Bug Components: plugins Reporter: Sercan Tekin Fix For: 3.0.0, 2.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-768) Hive Metastore Plugin
[ https://issues.apache.org/jira/browse/RANGER-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563203#comment-17563203 ] Sercan Tekin commented on RANGER-768: - [~rmani], any action should be taken on Ranger side? Such as activating the new cases here https://github.com/apache/ranger/blob/master/hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java#L162-L171 > Hive Metastore Plugin > - > > Key: RANGER-768 > URL: https://issues.apache.org/jira/browse/RANGER-768 > Project: Ranger > Issue Type: New Feature > Components: admin, plugins >Reporter: Yan >Assignee: Ramesh Mani >Priority: Major > Fix For: 2.1.0 > > Attachments: Design Proposal for Hive Metastore Plugin of Ranger - > V1.2.docx, Design Proposal for Hive Metastore Plugin of Ranger - V1.3.docx, > Design Proposal for Hive Metastore Plugin of Ranger - V1.4.docx, Design > Proposal for Hive Metastore Plugin of Ranger.docx, Design Proposal for Hive > Metastore Plugin of Ranger.docx > > > Currently there is no Ranger processing of Hive table meta store events that > could result in privilege modifications. One example is that when a table is > renamed by a Hive Server 2 client (the "beeline"), no proper privilege > adjustments in Ranger are made to allow/deny previously allowed/denied users > the same privileges as before. In addition, more advanced features, such as > granting/denying similar accesses to Hive's HDFS data to users that have (or > do not have) privileges in the Hive, would require that detailed metadata of > the Hive table, the storage info to be specific, be available to Ranger in > order to make the corresponding HDFS data accessible to the Hive users > directly. > This plugin will depend upon the existing Ranger Hive plugin, so it shares > the same "service" name as the associated Ranger Hive service deployed, and > it will be "co-enabled" with the existing Ranger Hive plugin. > Design doc will come soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
