<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Datapipeline-LookUp-Lakehouse in Pipelines</title>
    <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3380667#M539</link>
    <description>&lt;LI-CODE lang="markup"&gt;Hi,

This would only work if there is a lakehouse in both workspaces and it would only work as a source, not as a destination.

I understand that if I would like to break down the pipelines in different workspaces for organization purposes, I couldn't.

Kind Regards,

Dennes&lt;/LI-CODE&gt;</description>
    <pubDate>Tue, 15 Aug 2023 13:07:43 GMT</pubDate>
    <dc:creator>DennesTorres</dc:creator>
    <dc:date>2023-08-15T13:07:43Z</dc:date>
    <item>
      <title>Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3376121#M509</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Look up activty in data pipeline has query option only for external data store type (for azure sql database) but when i select the delta table i cant able to query. what are the other option we could use it to run a query against lakehouse tables in pipeline.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2023 10:31:00 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3376121#M509</guid>
      <dc:creator>Mathan1787</dc:creator>
      <dc:date>2023-08-11T10:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3377033#M514</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Query the lakehouse is possible. The lookup activity has two options : Workspace and External.&lt;BR /&gt;&lt;BR /&gt;The workspace option allow you to query the lakehouse.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;What seems to be a limitation, and may be you could add this into the "Ideas" area, is that "Workspace" requires the lakehouse to be in the same workspace as the pipeline.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In some cases, if you would like to access a different lakehouse, but you have one in the same workspace, maybe you could create a view in the one on the same workspace making a query to the external one?&lt;BR /&gt;&lt;BR /&gt;Kind Regards,&lt;BR /&gt;&lt;BR /&gt;Dennes&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2023 21:06:30 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3377033#M514</guid>
      <dc:creator>DennesTorres</dc:creator>
      <dc:date>2023-08-11T21:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3377728#M522</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;One possible workaround is to use a SQL Database connection and point to the lakehouse SQL Endpoint. It's not a perfect solution, but probably will work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dennes&lt;/P&gt;</description>
      <pubDate>Sun, 13 Aug 2023 10:26:09 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3377728#M522</guid>
      <dc:creator>DennesTorres</dc:creator>
      <dc:date>2023-08-13T10:26:09Z</dc:date>
    </item>
    <item>
      <title>Re: Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3378231#M525</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Could you vote on Fabric idea&amp;nbsp;&lt;A href="https://community.fabric.microsoft.com/t5/Data-Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3376121#M509" target="_blank" rel="noopener"&gt;OneLake Connector to work across workspaces in Data Factory in Fabric&lt;/A&gt;&amp;nbsp;?&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 03:29:42 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3378231#M525</guid>
      <dc:creator>GraceGu</dc:creator>
      <dc:date>2023-08-14T03:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3378455#M527</link>
      <description>&lt;P&gt;Thanks sql end point worked in this case. it would be great to have a query option for lakehouse.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 07:31:25 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3378455#M527</guid>
      <dc:creator>Mathan1787</dc:creator>
      <dc:date>2023-08-14T07:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3379674#M529</link>
      <description>&lt;P&gt;Even the cross workspace limitation should be addressable by creating a shortcut to the remote lakehouse, in the current workspace.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 20:27:40 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3379674#M529</guid>
      <dc:creator>ajarora</dc:creator>
      <dc:date>2023-08-14T20:27:40Z</dc:date>
    </item>
    <item>
      <title>Re: Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3380667#M539</link>
      <description>&lt;LI-CODE lang="markup"&gt;Hi,

This would only work if there is a lakehouse in both workspaces and it would only work as a source, not as a destination.

I understand that if I would like to break down the pipelines in different workspaces for organization purposes, I couldn't.

Kind Regards,

Dennes&lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 15 Aug 2023 13:07:43 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3380667#M539</guid>
      <dc:creator>DennesTorres</dc:creator>
      <dc:date>2023-08-15T13:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: Datapipeline-LookUp-Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3381427#M542</link>
      <description>&lt;P&gt;You basically have a LH1 in Workspace1, and Pipeline with Lookup activity in Workspace2. Can you create a LH2 in Workspace2, which points to the LH1 in Workspace1, and use lookup activity against LH2 ?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Aug 2023 23:10:10 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Datapipeline-LookUp-Lakehouse/m-p/3381427#M542</guid>
      <dc:creator>ajarora</dc:creator>
      <dc:date>2023-08-15T23:10:10Z</dc:date>
    </item>
  </channel>
</rss>

