Github user orhankislal commented on the issue:
https://github.com/apache/madlib/pull/325
@iyerr3 @jingyimei I'll put the following in the commit message before
merging.
This commit fixes the following potential issue.
1. User deploys MADlib on the schema `madlib1`.
2. Us
Github user jingyimei commented on the issue:
https://github.com/apache/madlib/pull/325
> @orhankislal Since this is a really big change, could you please add more
info in the commit on why this change is necessary and the best available
solution?
+ 1
---
Github user iyerr3 commented on the issue:
https://github.com/apache/madlib/pull/325
@orhankislal Since this is a really big change, could you please add more
info in the commit on why this change is necessary and the best available
solution?
---
Github user asfgit commented on the issue:
https://github.com/apache/madlib/pull/325
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/690/
---
GitHub user orhankislal opened a pull request:
https://github.com/apache/madlib/pull/325
Madpack/ic func schema
IC/DC was prone to failure if the user were creating tables in the
madlib schema. This commit fixes the potential issue by removing the
madlib from the search path
Github user orhankislal closed the pull request at:
https://github.com/apache/madlib/pull/324
---
GitHub user orhankislal opened a pull request:
https://github.com/apache/madlib/pull/324
Madpack/ic func schema
IC/DC was prone to failure if the user were creating tables in the
madlib schema. This commit fixes the potential issue by removing the
madlib from the search path
Github user orhankislal closed the pull request at:
https://github.com/apache/madlib/pull/322
---
