Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
All
-
-
Small
Description
See linked issue for full bug description.
The strange behavior (exception thrown plus a correct schema passed to stdout) comes from a bug in TacokitGuessSchema class (an exception is raised but shoudln't in that case).
Here's the normal process for the guess schema process for connector (processor in start of job):
the executeDiscoverSchemaExtendedAction is tried. (where is thrown "Not allowed to execute the HTTP call to retrieve the schema.")
if it failed, it tries to execute guessOutputComponentSchemaThroughResult which simulates the processor lifecycle and parse row outputed.
Attachments
Issue Links
- duplicates
-
TCOMP-2710 Unable to guess schema - improve workflow and exception throwing/handling
-
- Done
-
- is related to
-
TCOMP-2342 httpclient - Guesschema displays dialogbox to execute the connector if it can't be inferred.
-
- Done
-
-
TCOMP-2629 [Studio] Guess schema for Processor doesn't work when it has additional subjob
-
- Rejected
-