<?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>question Re: Do secondary indexes require that all rows have values for the indexed column? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Do-secondary-indexes-require-that-all-rows-have-values-for/m-p/160788#M24668</link>
    <description>&lt;P&gt;Two questions.&lt;/P&gt;&lt;P&gt;1) Yes if data is upsert via Phoenix. HBase does not store null values in cells, however, Phoenix enters some dummy/empty values in order to be able to select all rows associated with a column. There was a bug couple years that was fixed: PHOENIX-63.&lt;/P&gt;&lt;P&gt;2) No. Even dynamic columns are defined after the table in the FROM clause on a SELECT statement, they are just encoded binary and only understood at the runtime. Indexes are populated on CREATE INDEX on explicit columns. You could get creative by using a virtual column, but that would require more storage and some tricks on the actual SQL and performance may be bad.&lt;/P&gt;</description>
    <pubDate>Fri, 22 Apr 2016 02:40:51 GMT</pubDate>
    <dc:creator>cstanca</dc:creator>
    <dc:date>2016-04-22T02:40:51Z</dc:date>
    <item>
      <title>Do secondary indexes require that all rows have values for the indexed column?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Do-secondary-indexes-require-that-all-rows-have-values-for/m-p/160787#M24667</link>
      <description>&lt;P&gt;Can I add a secondary index to a dynamic column defined as part of a view?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2016 02:39:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Do-secondary-indexes-require-that-all-rows-have-values-for/m-p/160787#M24667</guid>
      <dc:creator>rgelhausen</dc:creator>
      <dc:date>2016-04-08T02:39:21Z</dc:date>
    </item>
    <item>
      <title>Re: Do secondary indexes require that all rows have values for the indexed column?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Do-secondary-indexes-require-that-all-rows-have-values-for/m-p/160788#M24668</link>
      <description>&lt;P&gt;Two questions.&lt;/P&gt;&lt;P&gt;1) Yes if data is upsert via Phoenix. HBase does not store null values in cells, however, Phoenix enters some dummy/empty values in order to be able to select all rows associated with a column. There was a bug couple years that was fixed: PHOENIX-63.&lt;/P&gt;&lt;P&gt;2) No. Even dynamic columns are defined after the table in the FROM clause on a SELECT statement, they are just encoded binary and only understood at the runtime. Indexes are populated on CREATE INDEX on explicit columns. You could get creative by using a virtual column, but that would require more storage and some tricks on the actual SQL and performance may be bad.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2016 02:40:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Do-secondary-indexes-require-that-all-rows-have-values-for/m-p/160788#M24668</guid>
      <dc:creator>cstanca</dc:creator>
      <dc:date>2016-04-22T02:40:51Z</dc:date>
    </item>
  </channel>
</rss>

