Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Azure Data Factory "Unknown linked service type: LakeHouse" #47648

Open
mikeblakeuk opened this issue Dec 23, 2024 · 1 comment
Open

[BUG] Azure Data Factory "Unknown linked service type: LakeHouse" #47648

mikeblakeuk opened this issue Dec 23, 2024 · 1 comment
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Data Factory Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@mikeblakeuk
Copy link

mikeblakeuk commented Dec 23, 2024

Library name and version

Azure.ResourceManager.DataFactory 1.5.0

Describe the bug

when creating a Linked Service to the Lakehouse and then using it an a DataFlow, Azure Data Factory reports

java.lang.Exception: Unknown linked service type: LakeHouse

Image

Note; View error details doesn't work (main.5e59cc067c06e579.js:1 ERROR TypeError: Cannot read properties of undefined (reading 'referenceName'))

Expected behavior

It works with the previous version of the DataFactory SDK with our own LinkedService and the type set to Lakehouse

Actual behavior

The DataFactory creates but the Flow doesn't complete.

This could be related to the previous issue #43786
Which was due to a bot fixing a spelling error.

Reproduction Steps

using Azure.ResourceManager.DataFactory;

var linkedServiceProperty = new LakeHouseLinkedService
{
  Tenant = fabricLakehouseLinkedService.TenantId,
  WorkspaceId = fabricLakehouseLinkedService.WorkspaceId,
  ArtifactId = fabricLakehouseLinkedService.LakehouseId,
  ServicePrincipalId = fabricIdentity.ClientId,
  ServicePrincipalCredential = new DataFactorySecretString(fabricIdentity.ClientSecret)
};

var linkedService = ArmDataFactoryModelFactory.DataFactoryLinkedServiceData(
    name: linkedServiceName,
    id: DataFactoryLinkedServiceResource.CreateResourceIdentifier(string.Empty, string.Empty, string.Empty, linkedServiceName),
    properties: linkedServiceProperty
);

Environment

Azure with C# net8.0
IDE VS 17.12.3

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 23, 2024
@jsquire jsquire added Data Factory Service Attention Workflow: This issue is responsible by Azure service team. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Dec 23, 2024
@ArthurMa1978
Copy link
Member

Thank you for your feedback @mikeblakeuk , @ruowan please help to look into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Data Factory Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

4 participants