WT-12083 Extend conn_api.c to support new get_configuration method

[y123456yz]

get connection configure string surport, connection api surport get_configure.

[wiredtiger-pr-bot]

Hi @y123456yz, thank you for your submission!
Please make sure to sign our Contributor Agreement (if you haven't already) and provide us with editor permissions on your branch. Instructions on how do that can be found here.

[y123456yz]

The background is as follows:

db.adminCommand( { setParameter : 1, "wiredTigerEngineRuntimeConfig" : "io_capacity=(total=110M)"})
{ "was" : "", "ok" : 1 }

db.adminCommand( { setParameter : 1, "wiredTigerEngineRuntimeConfig" : "eviction=(threads_min=8, threads_max=12)"})
{ "was" : "io_capacity=(total=110M)", "ok" : 1 }

db.adminCommand( { setParameter : 1, "wiredTigerEngineRuntimeConfig" : "verbose=[api:5]"})
{ "was" : "eviction=(threads_min=8, threads_max=12)", "ok" : 1 }

db.adminCommand( { getParameter : "1", wiredTigerEngineRuntimeConfig : 1 } )
{ "wiredTigerEngineRuntimeConfig" : "verbose=[api:5]", "ok" : 1 }

When we modify the configuration information of WT multiple times, Mongo server can only retain the last result and cannot obtain all modification records.

[y123456yz]

after wt merge this PR's code, I will add a PR to mongo server, perfect "db.adminCommand( { getParameter : "1", wiredTigerEngineRuntimeConfig : 1 } )", By get_configure api to obtain complete wt configuration information.

[y123456yz]

WT-12083

[y123456yz]

@clarissecheah
I have change the code, please review again.
thanks.

[clarissecheah]

Didn't pick this one up earlier - sorry! This should be:

__conn_get_configuration instead of __conn_get_home

I believe this will fix the s_all issue we have in the evergreen patch failure.

[clarissecheah]

Hi @y123456yz, one more thing - there's currently a known issue being fixed in clang analyzer that's causing the Evergreen patch failure we see. Could you merge the develop branch into your branch when you fix the comment I mentioned above? I'll re-review after, but this PR looks good to go after that. Thanks!

[y123456yz]

Hi @y123456yz, one more thing - there's currently a known issue being fixed in clang analyzer that's causing the Evergreen patch failure we see. Could you merge the develop branch into your branch when you fix the comment I mentioned above? I'll re-review after, but this PR looks good to go after that. Thanks!

hi, @clarissecheah
I have change the comment and run the newest s_all.
thanks.

[clarissecheah]

Hi @y123456yz , it appears as though s_all is still failing in the patch build. See below:

.947] + echo ####################### MESSAGE ############################
[2023/12/19 09:44:03.947] ####################### MESSAGE ############################
[2023/12/19 09:44:03.947] + echo s_all run of: "./s_clang_format " resulted in:
[2023/12/19 09:44:03.947] s_all run of: "./s_clang_format " resulted in:
[2023/12/19 09:44:03.948] + sed -e s/^/ / __wt.38565
[2023/12/19 09:44:03.948]  Modifying examples/c/ex_all.c

Could I just double check that you've run s_all and committed any changes (e.g. in s_clang_format)?

[y123456yz]

s_clang_format

hi, @clarissecheah
I merge the develop and run s_all again, It should be okay this time.

you can feel free to modify my code branches, If there are any other problems, Please help me with this.

thanks.
:)

[clarissecheah]

LGTM

[y123456yz]

the mongo server PR:
mongodb/mongo#1587