Re: UDFs and 1.3

Hi Stefan, This is correct : you need to add your package to drill.classpath.scanning. packages However, you don't need to add your classes to drill.classpath.scanning. base.classes This is because they extend the base classes that drill already defines here:

Re: UDFs and 1.3

Hi, I re did everything and update the drill-module.conf with this: drill { classpath.scanning { base.classes : ${?drill.classpath.scanning.base.classes} [ com.activitystream.drill.DirUtils, com.activitystream.drill.IPUtils, com.activitystream.drill.ListUtils,

UDFs and 1.3

Hi, I have a small set of UDFs that I have been running with Drill 1.1/1.2 which I'm trying to get working with 1.3 to no avail. It's as if the library is no picked up correctly even though the error I get indicates a missing function signature (variant): Error: VALIDATION ERROR: From line 1,

Re: UDFs and 1.3

Hi, Now they are but the outcome remains the same. Any additional pointers? Regards, -Stefan On Mon, Nov 9, 2015 at 7:21 PM, Stefán Baxter wrote: > Hi Nathan, > > thank you for a prompt reply. > > I thought the were but they are in fact compiled with the 1.2

Re: UDFs and 1.3

Hi Nathan, thank you for a prompt reply. I thought the were but they are in fact compiled with the 1.2 dependency (from maven) but they are placed in the correct place :) I will correct this and continue. Regards, -Stefán On Mon, Nov 9, 2015 at 7:15 PM, Nathan Griffith

Re: UDFs and 1.3

I don't think the compilation needs to be changed as there were no interface changes. However, we did get much more strict about making sure your drill-module.conf points at the right package names. Note here, specifically the addition of package names: