Fixed presto UDF patch broken link (#41)

Co-authored-by: Sushant Raikar <[email protected]>
linkedin · Mar 12, 2020 · 50326fe · 50326fe
1 parent edd7db6
commit 50326fe
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 1 deletion.
diff --git a/...documentation/transport-udfs-presto.patch → docs/transport-udfs-presto.patch b/...documentation/transport-udfs-presto.patch → docs/transport-udfs-presto.patch
diff --git a/docs/using-transport-udfs.md b/docs/using-transport-udfs.md
@@ -86,7 +86,7 @@ If the UDF class is `com.linkedin.transport.example.ExampleUDF` then the platfor
 Unlike Hive and Spark, Presto currently does not allow dynamically loading jar files once the Presto server has started.
 In Presto, the jar is deployed to the `plugin` directory.
 However, a small patch is required for the Presto engine to recognize the jar as a plugin, since the generated Presto UDFs implement the `SqlScalarFunction` API, which is currently not part of Presto's SPI architecture.
-You can find the patch [here](transportable-udfs-documentation/transport-udfs-presto.patch) and apply it before deploying your UDFs jar to the Presto engine.
+You can find the patch [here](transport-udfs-presto.patch) and apply it before deploying your UDFs jar to the Presto engine.
 
 2. Call the UDF in a query  
     To call the UDF, you will need to use the function name defined in the Transport UDF definition.