locked
Data Factory Project Config file - Unexpected character while parsing path RRS feed

  • Question

  • Hi,

    In the data factory project, we have added a config file which will replace value based on environment we are deploying in. There is one pipeline which calls Machine learning web service. The web service parameter names have spaces. Example "Database Server Name", "Table Name".

    My Config file contains configuration as follows:

        "MyMLPipeline": [
            {
                "name": "$.properties.activities[1].typeProperties.webServiceParameters.'Database server name'",
                "value": "MyAsqlServer.database.windows.net"
            }

    On compiling the project, the values are not replaced as configured but following statement can be seen in build output.

    We couldn't replace malformed property $.properties.activities[1].typeProperties.webServiceParameters.'Database server name1': Unexpected character while parsing path: 

    This issue is observed only when there is space in the node\element name. Is there any other way of handling this?

    Wednesday, February 3, 2016 2:33 PM

Answers

  • The Json.net library version that we use doesn’t support spaces in the Property keys. So you need to have the keys without spaces. This is a by design behavior of the Json.net library version we use. However you can try the following as a work around.
    Azure ML global parameters belong to, for example, reader and writer modules in the ML experiment. They are created with these default names that contain spaces, but they can be renamed. The owner of the ML experiment would have to log into ML Studio, rename the parameters, re-run the model(s), and re-publish the endpoint(s) (or, publish new endpoint so as to not break existing automations). There are cases we have seen where the team trying to run scoring does not actually own the experiment and is not able to make this change.

    Our product team is looking at the issue to see if there can be a fix within AFD but at this time we do not have a confirmation or timeline.

    Monday, February 15, 2016 5:37 PM