[
https://issues.apache.org/jira/browse/MADLIB-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273632#comment-16273632
]
ASF GitHub Bot commented on MADLIB-1184:
----------------------------------------
GitHub user njayaram2 opened a pull request:
https://github.com/apache/madlib/pull/207
Infra: Install MADlib on non-default schema in Jenkins
The Jenkins build that runs for every PR and for every master
commit is great. Installing MADlib on a non-default schema name
such as `mad` would help us identify many issues early (issues
that correspond to hard-coding `madlib` in the code/tests).
PS: The Jenkins build for this PR is expected to fail due to
https://issues.apache.org/jira/browse/MADLIB-1184
Closes #207
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/njayaram2/madlib
infra/jenkins_non_default_schema
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/madlib/pull/207.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #207
----
commit 5364ed5506538943c190f49a47d5607ac9bea07a
Author: Nandish Jayaram <[email protected]>
Date: 2017-11-30T23:05:27Z
Infra: Install MADlib on non-default schema in Jenkins
The Jenkins build that runs for every PR and for every master
commit is great. Installing MADlib on a non-default schema name
such as `mad` would help us identify many issues early (issues
that correspond to hard-coding `madlib` in the code/tests).
PS: The Jenkins build for this PR is expected to fail due to
https://issues.apache.org/jira/browse/MADLIB-1184
Closes #207
----
> k-NN install check fails on non-madlib schema name
> --------------------------------------------------
>
> Key: MADLIB-1184
> URL: https://issues.apache.org/jira/browse/MADLIB-1184
> Project: Apache MADlib
> Issue Type: Bug
> Components: k-NN
> Reporter: Nandish Jayaram
> Fix For: v1.13
>
>
> The install check fails when MADlib is installed on a schema named
> anything other than `madlib`. The issue seems to be because the fn_dist
> param expects a distance function name prefixed with `<madlib_schema>.`
> With MADlib installed on schema `mad`, the following error happens:
> {code}
> psql:/tmp/madlib.OIue8c/knn/test/knn.sql_in.tmp:155: ERROR:
> spiexceptions.InvalidSchemaName: schema "madlib" does not exist
> LINE 3: oid='madlib.squared_dist_norm2(DOUBLE PRECIS...
> ^
> QUERY: select prorettype != 'DOUBLE PRECISION'::regtype
> OR proisagg = TRUE AS OUTPUT from pg_proc where
> oid='madlib.squared_dist_norm2(DOUBLE PRECISION[], DOUBLE
> PRECISION[])'::regprocedure;
> CONTEXT: Traceback (most recent call last):
> PL/Python function "knn", line 35, in <module>
> fn_dist
> PL/Python function "knn", line 147, in knn
> PL/Python function "knn", line 100, in knn_validate_src
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
