Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Resolving this as most of the sub-tasks are resolved. The ones remaining are nice to haves, which I'll move out of this task.
Description
Currently server-side trusted extensions are supported (see FALCON-634 for more details).
Need to extend the Falcon Extensions to support extensions built by users. For example, lets say a user wants to add an extension for "data-quality check". This shouldn't require it to be compiled and tested with Falcon build. User should be able to add it on-the-fly (while the Falcon Server is running) and other users should be able to discover it, and "instantiate" this new extension.
Attachments
Attachments
Issue Links
- is blocked by
-
FALCON-2266 Non-intuitive response while registering/unregistering/submitting extension via server
- Resolved
-
FALCON-2267 Definition api fails if resources are empty
- Resolved
-
FALCON-2268 Extension list api does not follow default ASC order
- Resolved
-
FALCON-2270 Extension job details returns incomplete response
- Resolved
-
FALCON-2271 Scheduling non existing job fails with non intuitive response
- Resolved
-
FALCON-2272 Extension update succeeds while it is disabled
- Resolved
-
FALCON-2274 Job list in extension is failing with IllegalArgumentException
- Resolved
-
FALCON-2275 Unable to list instances of an extension
- Resolved
-
FALCON-2276 FalconCLIException while submitting trusted extension job
- Resolved
-
FALCON-2277 Incorrect error message on registering trusted exceptions
- Resolved
-
FALCON-2283 Internal Server Error : On trying to submit a trusted extension job
- Resolved
-
FALCON-2284 Error while listing extension jobs
- Resolved
-
FALCON-2286 Falcon upgradation fails to create new tables
- Resolved
-
FALCON-2287 Extension list fails with MIME type error on server
- Resolved
-
FALCON-2292 User Extension submission is failing because of the validate late inputs
- Resolved
-
FALCON-2269 Extension api fails via server in distributed mode
- Closed
- is related to
-
FALCON-2245 Improve error message for submitting job during extension jobName check
- Open
-
FALCON-2213 Falcon logs does not contain response message when recipe operations are performed.
- Resolved
-
FALCON-2214 Falcon extension registered without fully qualified hdfs path
- Resolved
-
FALCON-2215 Extension job submission throws non intuitive error
- Resolved
-
FALCON-2217 Job submission should fail with extension not registered.
- Resolved
-
FALCON-2224 Change return type of extension APIs to APIResult
- Resolved
-
FALCON-2239 Falcon extension definition feature is broken
- Resolved
-
FALCON-2240 Enable/disable feature is broken
- Resolved
-
FALCON-2241 Job submission for registered extension is broken
- Resolved
-
FALCON-2242 Extension validate feature is broken
- Resolved
-
FALCON-2243 Extension validation does not check job existance
- Resolved
-
FALCON-2261 Job submission fails with IllegalArgumentException
- Resolved
-
FALCON-2264 Error response returns object instead of response-message
- Resolved
-
FALCON-2221 Submitting an existing job fails with MySQLIntegrityConstraintViolationException
- Resolved
-
FALCON-2246 Api to list all the jobs in the system (and what extensions do they refer to)
- Resolved
-
FALCON-2247 Include status of the entities of the extensionJob in getDetailExtensionJobs
- Resolved
-
FALCON-2216 Recipe job submission api is non intutive
- Resolved
- relates to
-
FALCON-2238 Falcon extension describe feature is broken
- Resolved