<?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: a usecase to query millions of values. in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/a-usecase-to-query-millions-of-values/m-p/15410#M9741</link>
    <description>&lt;P&gt;You can also create a temporary view with the output from python code (one id = one row) and then inner join the view to the table. IMO will improve readability of your code.&lt;/P&gt;</description>
    <pubDate>Thu, 22 Dec 2022 13:06:06 GMT</pubDate>
    <dc:creator>daniel_sahal</dc:creator>
    <dc:date>2022-12-22T13:06:06Z</dc:date>
    <item>
      <title>a usecase to query millions of values.</title>
      <link>https://community.databricks.com/t5/data-engineering/a-usecase-to-query-millions-of-values/m-p/15409#M9740</link>
      <description>&lt;P&gt;have a small use case where we need to query the sql database with 1 million values(dynamically returned from python code) in the condition from python function. eg: select * from id in (1,2,23,33........1M).&amp;nbsp;I feel this is very bad approach. Is there any better way to query the millions of values using select query.&lt;/P&gt;&lt;P&gt;Kindly suggest.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2022 12:11:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/a-usecase-to-query-millions-of-values/m-p/15409#M9740</guid>
      <dc:creator>KVNARK</dc:creator>
      <dc:date>2022-12-21T12:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: a usecase to query millions of values.</title>
      <link>https://community.databricks.com/t5/data-engineering/a-usecase-to-query-millions-of-values/m-p/15410#M9741</link>
      <description>&lt;P&gt;You can also create a temporary view with the output from python code (one id = one row) and then inner join the view to the table. IMO will improve readability of your code.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Dec 2022 13:06:06 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/a-usecase-to-query-millions-of-values/m-p/15410#M9741</guid>
      <dc:creator>daniel_sahal</dc:creator>
      <dc:date>2022-12-22T13:06:06Z</dc:date>
    </item>
  </channel>
</rss>

