[BUG] WorkflowNode Parsing Fails for type Instant and Nested Objects

[owaiskazi19]

What is the bug?

For the request like:

"llm": {
              "model_id": "ldzS04kBxRPZ5cnWrqpd",
              "parameters": {
                  "type": "hello"
              }
          }

the parsing for WorkflowNode fails with the below

{
    "error": "Can't get text on a START_OBJECT at 56:43"
}

and for the fieldsof type Instant

created_time: 12684646585

fails with the below

Current token (FIELD_NAME) not numeric, can not use numeric value accessors

How can one reproduce the bug?

1. Pass a nested object to the Create API to reproduce the first bug.
2. pass an instant value to the Create API to reproduce the second one.

What is the expected behavior?

Parsing should go through.

What is your host/environment?

Ubuntu

Do you have any screenshots?

If applicable, add screenshots to help explain your problem.

Do you have any additional context?

Add any other context about the problem.

[dbwiddis]

The nested maps was an intentional thing to stop infinite recursion. You need to encode "parameters" as a special case like this:

flow-framework/src/main/java/org/opensearch/flowframework/model/WorkflowNode.java

Lines 147 to 153 in 1092325

	if (PROCESSORS_FIELD.equals(inputFieldName)) {
	List<PipelineProcessor> processorList = new ArrayList<>();
	while (parser.nextToken() != XContentParser.Token.END_ARRAY) {
	processorList.add(PipelineProcessor.parse(parser));
	}
	userInputs.put(inputFieldName, processorList.toArray(new PipelineProcessor[0]));
	} else {

(But probably under START_OBJECT rather than the array)

[dbwiddis]

Current token (FIELD_NAME) not numeric, can not use numeric value accessors

Where are you trying to parse an Instant? You're trying to parse the field name not value here.

[owaiskazi19]

Current token (FIELD_NAME) not numeric, can not use numeric value accessors

Where are you trying to parse an Instant? You're trying to parse the field name not value here.

Pasted the wrong error message here but basically needed to add parsing for numbers. Handled both the cases in this PR: #198