User Profile

Jher12

Frequent Visitor

Joined 8 months ago

11 Posts4 LikesLikes received1 Solution

View All Badges

User Widgets

Contributions

Re: Warning When Attempting to Dynamically Name the Destination File During Export
Hi deborshi_nag Destination - on premise file share
6 months ago Place Data Engineering
648Views
0likes
1Comment
Warning When Attempting to Dynamically Name the Destination File During Export
Hi, I am using a Copy activity to extract data from a Lakehouse table by executing a SQL query in the Source section, and I am exporting the results as a CSV file. When I attempt to dynamically assign a name to the output file, I receive the warning shown in the image below. What are the best practices or supported methods for handling dynamic file names in this scenario? Any assistance would be appreciated.
Solved
6 months ago Place Data Engineering
Data Pipeline
734Views
0likes
4Comments
Re: Pipeline error - Can't access the pipeline
v-sgandrathi Thank you for this comment, I was able to pull the json for the pipeline, which allowed me to review the activities and find workspace items that were deleted.
7 months ago Place Fabric platform
2.1KViews
1like
0Comments
Re: Pipeline error - Can't access the pipeline
I am unable to open the pipeline and view the activities. Whenever I try to open it, an error is returned and the UI appears gray. Is there any other way to troubleshoot this issue since I cannot see the activities?
8 months ago Place Fabric platform
2.1KViews
0likes
0Comments
Re: Pipeline error - Can't access the pipeline
Additional info: When I try to open the pipeline, I see the following screen.
8 months ago Place Fabric platform
2.2KViews
0likes
0Comments
Pipeline error - Can't access the pipeline
Hello, Whenever I try to access the pipelines I’m currently working on, I receive the error shown below. These pipelines are still in development, and some activities are deactivated. I usually have access to these pipelines and can work on them; however, as of today, I’m unable to do so. I would greatly appreciate any assistance. Error: Failed to open resourceCould not load resource 'test pipeline - external file'. Please ensure no mistakes in the JSON and that referenced resources exist. Status: UnknownError, Possible reason: TypeError: Cannot read properties of undefined (reading 'referenceName')
Solved
8 months ago Place Fabric platform
Workspaces
2.2KViews
0likes
7Comments
Re: Mismatch Between Table Name Case in Lakehouse Explorer and SQL Analytics Endpoint
Yes
8 months ago Place Fabric platform
1.5KViews
1like
0Comments
Re: Mismatch Between Table Name Case in Lakehouse Explorer and SQL Analytics Endpoint
Thank you suparnababu8, your quick response helped guide me to a solution. I was able to resolve the issue by recreating the tables loading them from another data lakehouse while ensuring the table names retained their original casing by using the code below to create the tables. Code: spark.conf.set('spark.sql.caseSensitive', True) df.write.format("delta").mode("overwrite").save(path) spark.sql(f"CREATE TABLE `{table_name}` USING DELTA LOCATION '{path}'")
8 months ago Place Fabric platform
1.5KViews
2likes
1Comment
Re: Mismatch Between Table Name Case in Lakehouse Explorer and SQL Analytics Endpoint
Hi, Thank you for the response. Is there any way to rename the tables without dropping and recreating them with quotes?
8 months ago Place Fabric platform
1.6KViews
0likes
3Comments
Mismatch Between Table Name Case in Lakehouse Explorer and SQL Analytics Endpoint
Why does the Lakehouse Explorer display table names in all lowercase, while the SQL Analytics Endpoint Explorer shows them in the intended letter case? Whenever I create notebooks that use the spark.catalog function, the table names are returned in lowercase instead of their original mixed-case format. How can I fix this? Any assistance would be greatly appreciated. Thank you in advance.
Solved
8 months ago Place Fabric platform
Workspaces
1.6KViews
0likes
7Comments

Data Privacy

Microsoft Fabric Community and Privacy

To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.