HIVE-27862: Map propertyContent to a wrong column in package.jdo

[dengzhhu653]

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

Is the change a dependency upgrade?

How was this patch tested?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

The version of Java (11.0.8) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17.
Read more here

[ayushtkn]

Ideally the column name in METASTORE_DB_PROPERTIES should have been PROPERTY_CONTENT like other columns, but I think we have to live with it now, due to compat issues...

There is no test which was checking the output?

[dengzhhu653]

Ideally the column name in METASTORE_DB_PROPERTIES should have been PROPERTY_CONTENT like other columns, but I think we have to live with it now, due to compat issues...

There is no test which was checking the output?

There are some tests HMSDirectTest which are testing out the fetch or save of PROPERTY_CONTENT on derby, but they get through the test, not sure why.

[ayushtkn]

hmm, do we need to catch someone from HMS side to figure out why those tests aren't working? I think it isn't an ideal situation for us, these bugs will keep on coming if those tests aren't working the way they should

[dengzhhu653]

hmm, do we need to catch someone from HMS side to figure out why those tests aren't working? I think it isn't an ideal situation for us, these bugs will keep on coming if those tests aren't working the way they should

I filed a jira HIVE-27879 for this

[ayushtkn]

LGTM.
Thanx @dengzhhu653