<?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: Phoenix 4.6 on HDP 2.3 and 2.2 in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101616#M14327</link>
    <description>&lt;P&gt;Adding to &lt;A rel="user" href="https://community.cloudera.com/users/627/asinghal.html" nodeid="627"&gt;@Ankit Singhal&lt;/A&gt;'s answer, we did try to replace the jars and it worked. I have a write-up here: &lt;A href="https://superuser.blog/upgrading-apache-phoenix-hdp/"&gt;https://superuser.blog/upgrading-apache-phoenix-hdp/&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 18 Nov 2017 14:02:55 GMT</pubDate>
    <dc:creator>sanketplus</dc:creator>
    <dc:date>2017-11-18T14:02:55Z</dc:date>
    <item>
      <title>Phoenix 4.6 on HDP 2.3 and 2.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101611#M14322</link>
      <description>&lt;P&gt;I would like to upgrade to the latest phoenix version on two clusters, one stack is 2.3 the other is 2.2. Is this supported and what's the recommended upgrade method? Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2016 00:45:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101611#M14322</guid>
      <dc:creator>bcobb</dc:creator>
      <dc:date>2016-01-07T00:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: Phoenix 4.6 on HDP 2.3 and 2.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101612#M14323</link>
      <description>&lt;P&gt;HWX does not support upgrade of individual components except for Spark and that's a recent change. You need to upgrade the whole stack, Phoenix 4.6 is not supported by HWX yet, that said, nothing stops you from upgrading Phoenix yourself. Refer to the Phoenix docs for upgrade information &lt;A href="https://phoenix.apache.org/upgrading.html"&gt;https://phoenix.apache.org/upgrading.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Phoenix 4.6 has been out for some time and 4.7 is going to be out really soon, if you don't want to lose support with HWX, I suggest you wait for the next maintenance release and/or major release and 4.6 should be included.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2016 00:52:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101612#M14323</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-01-07T00:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: Phoenix 4.6 on HDP 2.3 and 2.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101613#M14324</link>
      <description>&lt;P&gt;Upgrading any component out of HDP is not recommended , however, you can upgrade to phoenix 4.6 with just changing phoenix-server.jar on all nodes with phoenix-4.6 server jar  and upgrading client jar to phoenix-4.6 . Updates in the schema will be automatically taken care by new phoenix-client jar.&lt;/P&gt;&lt;P&gt;And just look for upgrade option in bin/psql.py.&lt;/P&gt;&lt;P&gt;u,--upgrade                  Upgrades tables specified as arguments by
                               rewriting them with the correct row key for
                               descending columns. If no arguments are
                               specified, then tables that need to be
                               upgraded will be displayed without being
                               upgraded. Use the -b option to bypass the
                               rewrite if you know that your data does not
                               need to be upgrade. This would only be the
                               case if you have not relied on auto padding
                               for BINARY and CHAR data, but instead have
                               always provided data up to the full max
                               length of the column. See PHOENIX-2067 and
                               PHOENIX-2120 for more information. Note
                               that phoenix.query.timeoutMs and
                               hbase.regionserver.lease.period parameters
                               must be set very high to prevent timeouts
                               when upgrading.
&lt;/P&gt;&lt;P&gt;if you have data affected by above jira tickets.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2016 01:01:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101613#M14324</guid>
      <dc:creator>asinghal</dc:creator>
      <dc:date>2016-01-07T01:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: Phoenix 4.6 on HDP 2.3 and 2.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101614#M14325</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/1972/bcobb.html" nodeid="1972"&gt;@Brenden Cobb&lt;/A&gt;&lt;P&gt;&lt;A href="http://hortonworks.com/hdp/whats-new/"&gt;http://hortonworks.com/hdp/whats-new/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Phoenix 4.4 as of HDP 2.3 so if you want to test 4.6 then you have to download from phoenix site "not supported as of now" &lt;/P&gt;&lt;P&gt;&lt;A href="http://apache.spinellicreations.com/phoenix/"&gt;http://apache.spinellicreations.com/phoenix/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2016 01:01:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101614#M14325</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2016-01-07T01:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: Phoenix 4.6 on HDP 2.3 and 2.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101615#M14326</link>
      <description>&lt;P&gt;HDP follows different folder structure and it also creates various symlinks for jars and folders. If you had done it previously or you have any idea how to go about this, can you please share the details?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2017 20:17:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101615#M14326</guid>
      <dc:creator>sanketplus</dc:creator>
      <dc:date>2017-03-23T20:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: Phoenix 4.6 on HDP 2.3 and 2.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101616#M14327</link>
      <description>&lt;P&gt;Adding to &lt;A rel="user" href="https://community.cloudera.com/users/627/asinghal.html" nodeid="627"&gt;@Ankit Singhal&lt;/A&gt;'s answer, we did try to replace the jars and it worked. I have a write-up here: &lt;A href="https://superuser.blog/upgrading-apache-phoenix-hdp/"&gt;https://superuser.blog/upgrading-apache-phoenix-hdp/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 18 Nov 2017 14:02:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Phoenix-4-6-on-HDP-2-3-and-2-2/m-p/101616#M14327</guid>
      <dc:creator>sanketplus</dc:creator>
      <dc:date>2017-11-18T14:02:55Z</dc:date>
    </item>
  </channel>
</rss>

