Normal mode

In this case, run the same test as the applyopcpp case, but with a sample input file of:

+,1,2

To do so, specify the name of the UDF, the input file, the database, and the argument specification of the input file. You can also choose to print the output.

nzudxrunharness --name "apply" --file input.txt --print \
--varargs "varchar(10):int4:int4" --print
(clientmgr) Info: admin: login successful
Selected only choice
1 - APPLY() RETURNS FLOAT8
Executing /nz/kit/bin/adm/udxharness -f APPLY_func.harness -k /nz/kit

starting execution
in evaluate
DOUBLE: 3.000000
Elapsed time: 0m0.006s

External references
vtable for __cxxabiv1::__class_type_info
vtable for __cxxabiv1::__si_class_type_info
operator delete[](void*)
operator delete(void*)
operator new(unsigned int)
__cxa_begin_catch
__cxa_end_catch
__cxa_pure_virtual
__gxx_personality_v0
free
nzaeisoAdapUdfClose
nzaeisoAdapUdfCreate
nzaeisoAdapUdfGetReturn
nzaeisoAdapUdfGetSizerResult
nzaeisoAdapUdfSetController
nzaeisoAdapUdfSwitchToSizerMode
nzaeisoCtrlUdfClose
nzaeisoCtrlUdfCreate
nzaeisoCtrlUdfGetResult
nzaeisoCtrlUdfNewInput
nzaeisoCtrlUdfNoMoreInput
nzaeisoCtrlUdfSetAdapter
sprintf
strcmp
strdup
throwError

Our UDX object used 0 bytes (may be rounded up to nearest page 4096)
Our UDX return value takes up 8 bytes, with 669 bytes for miscellaneous
Our UDX arguments take up 30 bytes, with 34 bytes for miscellaneous
Our UDX state values take up 0 bytes, with 8 bytes for miscellaneous
State information may be doubled, since we need two states for merge