Filter function not found if created in a user schema

[monetdb-team]

Date: 2015-04-16 08:14:19 +0200
From: @swingbit
To: SQL devs <>
Version: 11.19.9 (Oct2014-SP2)
CC: @njnes

Last updated: 2015-08-28 13:41:50 +0200

Comment 20797

Date: 2015-04-16 08:14:19 +0200
From: @swingbit

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36
Build Identifier:

I created a filter function:

CREATE filter function strmaxdist(s1 string, s2 string, k int)
external name str.maxdist;

to be used as:

SELECT *
FROM a,b
WHERE a.s strmaxdist(2) b.s;

It works fine if I create and use the filter function in the "sys" schema.

If I create and use it when I am on a different schema, then I get:

Subquery result missing

Reproducible: Always

$ mserver5 --version
MonetDB 5 server v11.19.10 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.35 2014-04-04 (compiled with 8.35)
openssl: OpenSSL 1.0.1k 8 Jan 2015 (compiled with OpenSSL 1.0.1k-fips 8 Jan 2015)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: roberto@photon.spinque.com (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64

Comment 20798

Date: 2015-04-16 11:10:50 +0200
From: @swingbit

UPDATE:

If I issue the same CREATE FILTER FUNCTION command in both the "sys" and my custom schema, then I can successfully use the filter function in the custom schema.

Comment 20820

Date: 2015-04-19 21:48:21 +0200
From: @njnes

This is fixed (only) in default. There we changed filter functions calling interface as well (ie change to [a1,a2] filter.func [b1,b...].

Comment 21189

Date: 2015-08-28 13:41:50 +0200
From: @sjoerdmullender

Jul2015 has been released.