Couchbase Build Team added a comment - 08/Feb/22 6:51 AM Build couchbase-server-7.1.0-2259 contains query commit 2a1fdd4 with commit message: MB-50464 : Jsonschema parsing dependency for js-evaluator

Mihir Kamdar (Inactive) added a comment - 08/Feb/22 10:02 AM Abhishek Jindal can you pls help with details on how to validate this fix ?

Abhishek Jindal added a comment - 09/Feb/22 1:44 AM This patch adds ability to specify a global config to js-evaluator / JS-UDFs. We're currently accepting log_level (changes the logging level of JS-UDFs) and conn_pool_size (limits the number of open query iterators at a given point during UDF execution). Schema is as follows: { "log_level": integer between 1-6 "conn_pool_capacity" : integer between 1-20 } config can be accessed via the following endpoints (for JS-UDFs only Global External Functions Manage role is allowed): curl -v -s -k -X POST http://127.0.0.1:8096/evaluator/config -u Administrator:asdasd -H 'content-type: application/json' --data-binary @config.json curl -s -k -X GET http://127.0.0.1:8096/evaluator/config -u Administrator:asdasd — With this change users can now update the log level dynamically between Fatal (1) and Trace (6). And can change the connection pool size anytime during execution between 1-20 handles. Config is replicated over metakv across all query nodes.

Pierre Regazzoni added a comment - 11/Feb/22 4:53 PM Verified on 7.1.0-2281 # curl  -s -k -X GET http: //127.0.0.1:8093/evaluator/config -u Administrator:password {   "log_level" : 4 ,   "conn_pool_capacity" : 10 }   # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"log_level": 6}' { "status" : "OK" }   # curl  -s -k -X GET http: //127.0.0.1:8093/evaluator/config -u Administrator:password {   "log_level" : 6 ,   "conn_pool_capacity" : 10 }   # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"conn_pool_capacity": 8}' { "status" : "OK" }   # curl  -s -k -X GET http: //127.0.0.1:8093/evaluator/config -u Administrator:password {   "log_level" : 6 ,   "conn_pool_capacity" : 8 }   # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"conn_pool_capacity": 10, "log_level": 4}' { "status" : "OK" }   # curl  -s -k -X GET http: //127.0.0.1:8093/evaluator/config -u Administrator:password {   "log_level" : 4 ,   "conn_pool_capacity" : 10 } Invalid values: # curl-s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"conn_pool_capacity": 0}' Invalid globalGonfig schema, err: [I[#/conn_pool_capacity] S[#/properties/conn_pool_capacity/minimum] must be >= 1 but found 0 ]    # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"conn_pool_capacity": 21}'  Invalid globalGonfig schema, err: [I[#/conn_pool_capacity] S[#/properties/conn_pool_capacity/maximum] must be <= 20 but found 21 ]    # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"conn_pool_capacity": 50}'  Invalid globalGonfig schema, err: [I[#/conn_pool_capacity] S[#/properties/conn_pool_capacity/maximum] must be <= 20 but found 50 ]    # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"conn_pool_capacity": 20}'  { "status" : "OK" }   # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"log_level": 0}' Invalid globalGonfig schema, err: [I[#/log_level] S[#/properties/log_level/minimum] must be >= 1 but found 0 ]    # curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"log_level": 6}' { "status" : "OK" }[root @node1 ~]# curl -s -k -X POST http: //127.0.0.1:8093/evaluator/config -u Administrator:password -d '{"log_level": 7}' Invalid globalGonfig schema, err: [I[#/log_level] S[#/properties/log_level/maximum] must be <= 6 but found 7 ] Abhishek Jindal could error above be more human readable

Abhishek Jindal added a comment - 14/Feb/22 8:34 AM Pierre Regazzoni Currently couldn't find a better way of extracting the relevant error only. Hence, this might remain as is in Neo. Can re-work on this in later release as part of further work on js-evaluator's REST layer.