Harish, here are some additions to your list, with links and patch excerpts:
HIVE-5351 <https://issues.apache.org/jira/browse/HIVE-5351> (linked doc jira HIVE-6318 <https://issues.apache.org/jira/browse/HIVE-6318> doesn't provide definitions for template file but documents these config in the wiki -- Setting Up HiveServer2 - SSL Encryption<https://cwiki.apache.org/confluence/display/Hive/Setting+up+HiveServer2#SettingUpHiveServer2-SSLEncryption> ): + HIVE_SERVER2_USE_SSL("hive.server2.use.SSL", false), + HIVE_SERVER2_SSL_KEYSTORE_PATH("hive.server2.keystore.path", ""), + HIVE_SERVER2_SSL_KEYSTORE_PASSWORD("hive.server2.keystore.password", ""), HIVE-6447 (on your list): HIVE_CONVERT_JOIN_BUCKET_MAPJOIN_TEZ("hive.convert.join.bucket.mapjoin.tez", false), description provided in jira comment<https://issues.apache.org/jira/browse/HIVE-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959765#comment-13959765> : {code} <property> <name>hive.convert.join.bucket.mapjoin.tez</name> <value>false</value> <description>Whether joins can be automatically converted to bucket map joins in hive when tez is used as the execution engine.</description> </property> {code} HIVE-6500 <https://issues.apache.org/jira/browse/HIVE-6500>: HIVESTATSDBCLASS("hive.stats.dbclass", "fs", new PatternValidator("jdbc(:.*)", "hbase", "counter", "custom", "fs")), // StatsSetupConst.StatDB *Need to add "fs" to template description:* <name>hive.stats.dbclass</name> <value>counter</value> <description>The storage that stores temporary Hive statistics. Currently, jdbc, hbase, counter and custom type are supported.</description> HIVE-6466 <https://issues.apache.org/jira/browse/HIVE-6466> added a config value (PAM) and a new config (hive.server2.authentication.pam.services): HIVE_SERVER2_AUTHENTICATION("hive.server2.authentication", "NONE", - new StringsValidator("NOSASL", "NONE", "LDAP", "KERBEROS", "CUSTOM")), + new StringsValidator("NOSASL", "NONE", "LDAP", "KERBEROS", "PAM", "CUSTOM")), ... + // List of the underlying pam services that should be used when auth type is PAM + // A file with the same name must exist in /etc/pam.d + HIVE_SERVER2_PAM_SERVICES("hive.server2.authentication.pam.services", null), It's documented in the wiki by HIVE-6318<https://issues.apache.org/jira/browse/HIVE-6318>in Setting Up HiveServer2 - Pluggable Authentication Modules (PAM)<https://cwiki.apache.org/confluence/display/Hive/Setting+up+HiveServer2#SettingUpHiveServer2-PluggableAuthenticationModules(PAM)>and supposedly documented in the template file by HIVE-6503 <https://issues.apache.org/jira/browse/HIVE-6503>, which says committed for 0.13.0 but *doesn't show up in branch 13 or trunk.* HIVE-6503.1.patch<https://issues.apache.org/jira/secure/attachment/12633674/HIVE-6503.1.patch> : @@ -2165,6 +2165,7 @@ NONE: no authentication check LDAP: LDAP/AD based authentication KERBEROS: Kerberos/GSSAPI authentication + PAM: Pluggable authentication module CUSTOM: Custom authentication provider (Use with property hive.server2.custom.authentication.class) </description> @@ -2217,6 +2218,15 @@ </property> <property> + <name>hive.server2.authentication.pam.services</name> + <value></value> + <description> + List of the underlying PAM services that should be used when auth type is PAM. + A file with the same name must exist in /etc/pam.d. + </description> +</property> + +<property> <name>hive.server2.enable.doAs</name> <value>true</value> <description> HIVE-6681 <https://issues.apache.org/jira/browse/HIVE-6681>: + SERDESUSINGMETASTOREFORSCHEMA("hive.serdes.using.metastore.for.schema","org.apache.hadoop.hive.ql.io.orc.OrcSerde," + + "org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe,org.apache.hadoop.hive.serde2.columnar.ColumnarSerDe," + + "org.apache.hadoop.hive.serde2.dynamic_type.DynamicSerDe,org.apache.hadoop.hive.serde2.MetadataTypedColumnsetSerDe," + + "org.apache.hadoop.hive.serde2.columnar.LazyBinaryColumnarSerDe,org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe," + + "org.apache.hadoop.hive.serde2.lazybinary.LazyBinarySerDe"), That's it, as far as I can tell. -- Lefty On Wed, Apr 9, 2014 at 3:49 PM, Harish Butani <hbut...@hortonworks.com>wrote: > Lefty, here is the list I found missing from the template xml file: > > HIVE-6447: > > HIVE_CONVERT_JOIN_BUCKET_MAPJOIN_TEZ("hive.convert.join.bucket.mapjoin.tez", > false), > > HIVE-6492: > HIVELIMITTABLESCANPARTITION("hive.limit.query.max.table.partition", > -1), > > HIVE-5843: > // Transactions > HIVE_TXN_MANAGER("hive.txn.manager", > "org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager"), > // time after which transactions are declared aborted if the client has > // not sent a heartbeat, in seconds. > HIVE_TXN_TIMEOUT("hive.txn.timeout", 300), > > // Maximum number of transactions that can be fetched in one call to > // open_txns(). > // Increasing this will decrease the number of delta files created when > // streaming data into Hive. But it will also increase the number of > // open transactions at any given time, possibly impacting read > // performance. > HIVE_TXN_MAX_OPEN_BATCH("hive.txn.max.open.batch", 1000), > > // Whether to run the compactor's initiator thread in this metastore > instance or not. > HIVE_COMPACTOR_INITIATOR_ON("hive.compactor.initiator.on", false), > > // Number of compactor worker threads to run on this metastore > instance. > HIVE_COMPACTOR_WORKER_THREADS("hive.compactor.worker.threads", 0), > > // Time, in seconds, before a given compaction in working state is > declared a failure and > // returned to the initiated state. > HIVE_COMPACTOR_WORKER_TIMEOUT("hive.compactor.worker.timeout", 86400L), > > // Time in seconds between checks to see if any partitions need > compacted. This should be > // kept high because each check for compaction requires many calls > against the NameNode. > HIVE_COMPACTOR_CHECK_INTERVAL("hive.compactor.check.interval", 300L), > > // Number of delta files that must exist in a directory before the > compactor will attempt a > // minor compaction. > > HIVE_COMPACTOR_DELTA_NUM_THRESHOLD("hive.compactor.delta.num.threshold", > 10), > > // Percentage (by size) of base that deltas can be before major > compaction is initiated. > > HIVE_COMPACTOR_DELTA_PCT_THRESHOLD("hive.compactor.delta.pct.threshold", > 0.1f), > > // Number of aborted transactions involving a particular table or > partition before major > // compaction is initiated. > > HIVE_COMPACTOR_ABORTEDTXN_THRESHOLD("hive.compactor.abortedtxn.threshold", > 1000), > > > > On Apr 9, 2014, at 1:15 AM, Lefty Leverenz <leftylever...@gmail.com> > wrote: > > >> how much effort it would take to do HIVE-6586 > > > > One day of concentrated effort, but call it two days just in case I'm not > > concentrating. (Spring fever on the East Coast, where spring is a big > > deal.) > > > >> Regarding the missing params in hive-default: > > > > I can take care of that, thanks -- I've been flagging them in the mailing > > list. But if you have a good way to check, let's both do it. > > > >> What will it take to rebase. > > > > That's a question for Navis. I was assuming we would stick with the > > current patch and HIVE-6586 would update HiveConf.java. > > > >> Wasn't it reverted from the 0.13 branch? Don't recall the reason for > > this. Is that issue resolved now? > > > > Yes, there was a build issue (see Feb. 18th > > comments< > https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904584#comment-13904584 > >) > > and AFAIK the issue is resolved now (see comments on Feb. > > 23< > https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909988#comment-13909988 > >, > > Feb. 25< > https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912461#comment-13912461 > >, > > and Feb. 26-a< > https://issues.apache.org/jira/browse/HIVE-6037?focusedCommentId=13913412&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13913412 > > > > ... > > but also Feb. 26-b,< > https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913449#comment-13913449 > > > > Feb. > > 27< > https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914135#comment-13914135 > >, > > and March 12< > https://issues.apache.org/jira/browse/HIVE-6037?focusedCommentId=13932785&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13932785 > > > > 's patch for 0.13.0< > https://issues.apache.org/jira/secure/attachment/12634329/HIVE-6037-0.13.0 > > > > -- > > I had to add ".txt" for missing line breaks). > > > > Thanks. > > > > > > -- Lefty > > > > > > On Wed, Apr 9, 2014 at 2:49 AM, Harish Butani <hbut...@hortonworks.com > >wrote: > > > >> Lefty, good point. > >> I was assuming 6037 is not going into 0.13. Wasn't it reverted from the > >> 0.13 branch? > >> Don't recall the reason for this. Is that issue resolved now? > >> The last patch is from March 12th. What will it take to rebase. > >> > >> Seems safer to keep out of 0.13 and manually add the missing params. > >> But I will let the experts weigh in. > >> Regarding the missing params in hive-default: will try to get you the > >> missing ones by tomorrow. > >> If we decide to go with adding 6037 to 0.13: do you have a sense of how > >> much effort it would take to do HIVE-6586. > >> > >> regards, > >> Harish. > >> > >> On Apr 8, 2014, at 11:02 PM, Lefty Leverenz <leftylever...@gmail.com> > >> wrote: > >> > >>> What about HIVE-6037 <https://issues.apache.org/jira/browse/HIVE-6037> > >>> (Synchronize > >>> HiveConf with hive-default.xml.template and support show conf) and its > >>> followup HIVE-6586 <https://issues.apache.org/jira/browse/HIVE-6586>? > >>> > >>> Some new configs probably don't have definitions in > >>> hive-defaul.xml.template because I've been telling people not to bother > >>> with the template file, since it's going to be generated from > >> HiveConf.java > >>> soon. So if HIVE-6037 and -6586 aren't in 0.13.0, I'll have to create > >>> another jira for 0.13.0 to patch the template file. > >>> > >>> But if HIVE-6037 is in 0.13.0, then I have a fair amount of work to do > on > >>> HIVE-6586 -- otherwise several new configs won't be in HiveConf.java. > >>> > >>> -- Lefty > >>> > >>> > >>> On Wed, Apr 9, 2014 at 1:33 AM, Harish Butani <hbut...@hortonworks.com > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> We are getting close to having all the issues resolved. > >>>> I have the following list of open jiras as needing to go into 0.13 > >>>> 6863, 5687, 6604,6850,6818,6732,4904,5376, and 6319. > >>>> > >>>> These are all close to being committed. Some are waiting for the 24hr > >>>> period, a couple have been reviewed and +1ed, waiting for tests to > pass. > >>>> > >>>> So lets shoot for closing out all these issues by Thursday 12pm PST. > >>>> Would like to cut an rc by Thursday afternoon. > >>>> > >>>> regards, > >>>> Harish. > >>>> > >>>> > >>>> On Mar 26, 2014, at 7:14 PM, Prasanth Jayachandran < > >>>> pjayachand...@hortonworks.com> wrote: > >>>> > >>>>> Hi Harish > >>>>> > >>>>> Can we have the following bugs for 0.13? These bugs are related to > >>>> feature HIVE-6455 added as part of 0.13. > >>>>> https://issues.apache.org/jira/browse/HIVE-6748 (Resource leak bug) > >>>>> https://issues.apache.org/jira/browse/HIVE-6760 (Bug in handling > list > >>>> bucketing) > >>>>> https://issues.apache.org/jira/browse/HIVE-6761 (Bug with hashcodes > >>>> generation) > >>>>> > >>>>> Thanks > >>>>> Prasanth Jayachandran > >>>>> > >>>>> On Mar 26, 2014, at 1:22 PM, Hari Subramaniyan < > >>>> hsubramani...@hortonworks.com> wrote: > >>>>> > >>>>>> Hi Harish > >>>>>> Can you include HIVE-6708. It covers quite a number of issues > >> associated > >>>>>> with Vectorization(including some correctness issues and > exceptions). > >>>>>> > >>>>>> Thanks > >>>>>> Hari > >>>>>> > >>>>>> > >>>>>> On Tue, Mar 25, 2014 at 12:01 PM, Xuefu Zhang <xzh...@cloudera.com> > >>>> wrote: > >>>>>> > >>>>>>> Harish, > >>>>>>> > >>>>>>> Could we include HIVE-6740? > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Xuefu > >>>>>>> > >>>>>>> > >>>>>>> On Thu, Mar 20, 2014 at 7:27 PM, Prasanth Jayachandran < > >>>>>>> pjayachand...@hortonworks.com> wrote: > >>>>>>> > >>>>>>>> Harish, > >>>>>>>> > >>>>>>>> Could you add the following bugs as well? > >>>>>>>> Following are related to LazyMap bug > >>>>>>>> https://issues.apache.org/jira/browse/HIVE-6707 > >>>>>>>> https://issues.apache.org/jira/browse/HIVE-6714 > >>>>>>>> https://issues.apache.org/jira/browse/HIVE-6711 > >>>>>>>> > >>>>>>>> Following is NPE bug with orc struct > >>>>>>>> https://issues.apache.org/jira/browse/HIVE-6716 > >>>>>>>> > >>>>>>>> Thanks > >>>>>>>> Prasanth Jayachandran > >>>>>>>> > >>>>>>>> On Mar 14, 2014, at 6:26 PM, Eugene Koifman < > >> ekoif...@hortonworks.com > >>>>> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> could you add > >> https://issues.apache.org/jira/browse/HIVE-6676please. > >>>>>>>> It's > >>>>>>>>> a blocker as well. > >>>>>>>>> > >>>>>>>>> Thanks, > >>>>>>>>> Eugene > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Fri, Mar 14, 2014 at 5:30 PM, Vaibhav Gumashta < > >>>>>>>> vgumas...@hortonworks.com > >>>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>>> Harish, > >>>>>>>>>> > >>>>>>>>>> Can we have this in as well: > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6660. > >>>>>>>>>> Blocker bug in my opinion. > >>>>>>>>>> > >>>>>>>>>> Thanks, > >>>>>>>>>> --Vaibhav > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Fri, Mar 14, 2014 at 2:21 PM, Thejas Nair < > >>>> the...@hortonworks.com> > >>>>>>>>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> Harish, > >>>>>>>>>>> Can you also include HIVE-6673< > >>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6673> > >>>>>>>>>>> - show grant statement for all principals throws NPE > >>>>>>>>>>> This variant of 'show grant' is very useful, and the fix for > NPE > >> is > >>>>>>>>>>> straightforward. It is patch available now. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> On Fri, Mar 14, 2014 at 10:25 AM, Yin Huai < > >> huaiyin....@gmail.com> > >>>>>>>>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>>> Guys, > >>>>>>>>>>>> > >>>>>>>>>>>> Seems ConditionalResolverCommonJoin is not working correctly? > I > >>>>>>>> created > >>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6668 and set it > as a > >>>>>>>>>> blocker. > >>>>>>>>>>>> > >>>>>>>>>>>> thanks, > >>>>>>>>>>>> > >>>>>>>>>>>> Yin > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> On Fri, Mar 14, 2014 at 11:34 AM, Thejas Nair < > >>>>>>> the...@hortonworks.com > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>>> Can you also add HIVE-6647 < > >>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6647> to > >>>>>>>>>>>>> the list? It is marked as a blocker for 0.13. > >>>>>>>>>>>>> It has a necessary version number upgrade for HS2. It is > ready > >> to > >>>>>>> be > >>>>>>>>>>>>> committed. > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Fri, Mar 14, 2014 at 12:38 AM, Prasanth Jayachandran < > >>>>>>>>>>>>> pjayachand...@hortonworks.com> wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Harish > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Can you please make the following changes to my earlier > >> request? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> HIVE-4177 is not required.. instead the same work is tracked > >>>> under > >>>>>>>>>>>>>> HIVE-6578. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Can you also consider HIVE-6656? > >>>>>>>>>>>>>> HIVE-6656 is bug fix for ORC reader when reading timestamp > >>>>>>>>>>> nanoseconds. > >>>>>>>>>>>>>> This bug exists in earlier versions as well, so it will be > >> good > >>>>>>>>>> have > >>>>>>>>>>>> this > >>>>>>>>>>>>>> fixed in 0.13.0 > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Thanks > >>>>>>>>>>>>>> Prasanth Jayachandran > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On Mar 13, 2014, at 8:52 AM, Thejas Nair < > >>>> the...@hortonworks.com> > >>>>>>>>>>>> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Harish, > >>>>>>>>>>>>>>> I think we should include the following - > >>>>>>>>>>>>>>> HIVE-6547 - This is a cleanup of metastore api changes > >>>> introduced > >>>>>>>>>>> in > >>>>>>>>>>>>>> 0.13 . > >>>>>>>>>>>>>>> This can't be done post release. I will get a patch out in > >> few > >>>>>>>>>>> hours. > >>>>>>>>>>>>>>> HIVE-6567 - fixes a NPE in 'show grant .. on all" > >>>>>>>>>>>>>>> HIVE-6629 - change in syntax for 'set role none' . marked > as > >> a > >>>>>>>>>>>> blocker > >>>>>>>>>>>>>> bug. > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> On Tue, Mar 11, 2014 at 8:39 AM, Harish Butani < > >>>>>>>>>>>>> hbut...@hortonworks.com > >>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> yes sure. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On Mar 10, 2014, at 3:55 PM, Gopal V <gop...@apache.org> > >>>> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Can I add HIVE-6518 as well to the merge queue on > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>> > >>>>>>> > >>>> > >> > https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> It is a relatively simple OOM safety patch to vectorized > >>>>>>>>>>> group-by. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Tests pass locally for vec group-by, but the pre-commit > >> tests > >>>>>>>>>>>> haven't > >>>>>>>>>>>>>>>> fired eventhough it's been PA for a while now. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Cheers, > >>>>>>>>>>>>>>>>> Gopal > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>>>>>>>>>> NOTICE: This message is intended for the use of the > >> individual > >>>>>>>>>> or > >>>>>>>>>>>>>> entity to > >>>>>>>>>>>>>>>> which it is addressed and may contain information that is > >>>>>>>>>>>>> confidential, > >>>>>>>>>>>>>>>> privileged and exempt from disclosure under applicable > law. > >> If > >>>>>>>>>> the > >>>>>>>>>>>>>> reader > >>>>>>>>>>>>>>>> of this message is not the intended recipient, you are > >> hereby > >>>>>>>>>>>> notified > >>>>>>>>>>>>>> that > >>>>>>>>>>>>>>>> any printing, copying, dissemination, distribution, > >> disclosure > >>>>>>>>>> or > >>>>>>>>>>>>>>>> forwarding of this communication is strictly prohibited. > If > >>>> you > >>>>>>>>>>> have > >>>>>>>>>>>>>>>> received this communication in error, please contact the > >>>> sender > >>>>>>>>>>>>>> immediately > >>>>>>>>>>>>>>>> and delete it from your system. Thank You. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>>>>>>>>> NOTICE: This message is intended for the use of the > >> individual > >>>> or > >>>>>>>>>>>>> entity > >>>>>>>>>>>>>> to > >>>>>>>>>>>>>>> which it is addressed and may contain information that is > >>>>>>>>>>>> confidential, > >>>>>>>>>>>>>>> privileged and exempt from disclosure under applicable law. > >> If > >>>>>>>>>> the > >>>>>>>>>>>>> reader > >>>>>>>>>>>>>>> of this message is not the intended recipient, you are > hereby > >>>>>>>>>>>> notified > >>>>>>>>>>>>>> that > >>>>>>>>>>>>>>> any printing, copying, dissemination, distribution, > >> disclosure > >>>> or > >>>>>>>>>>>>>>> forwarding of this communication is strictly prohibited. If > >> you > >>>>>>>>>>> have > >>>>>>>>>>>>>>> received this communication in error, please contact the > >> sender > >>>>>>>>>>>>>> immediately > >>>>>>>>>>>>>>> and delete it from your system. Thank You. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> -- > >>>>>>>>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>>>>>>>> NOTICE: This message is intended for the use of the > individual > >>>> or > >>>>>>>>>>>> entity > >>>>>>>>>>>>> to > >>>>>>>>>>>>>> which it is addressed and may contain information that is > >>>>>>>>>>> confidential, > >>>>>>>>>>>>>> privileged and exempt from disclosure under applicable law. > If > >>>> the > >>>>>>>>>>>> reader > >>>>>>>>>>>>>> of this message is not the intended recipient, you are > hereby > >>>>>>>>>>> notified > >>>>>>>>>>>>> that > >>>>>>>>>>>>>> any printing, copying, dissemination, distribution, > disclosure > >>>> or > >>>>>>>>>>>>>> forwarding of this communication is strictly prohibited. If > >> you > >>>>>>>>>> have > >>>>>>>>>>>>>> received this communication in error, please contact the > >> sender > >>>>>>>>>>>>> immediately > >>>>>>>>>>>>>> and delete it from your system. Thank You. > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> -- > >>>>>>>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>>>>>>> NOTICE: This message is intended for the use of the > individual > >> or > >>>>>>>>>>> entity > >>>>>>>>>>>> to > >>>>>>>>>>>>> which it is addressed and may contain information that is > >>>>>>>>>> confidential, > >>>>>>>>>>>>> privileged and exempt from disclosure under applicable law. > If > >>>> the > >>>>>>>>>>> reader > >>>>>>>>>>>>> of this message is not the intended recipient, you are hereby > >>>>>>>>>> notified > >>>>>>>>>>>> that > >>>>>>>>>>>>> any printing, copying, dissemination, distribution, > disclosure > >> or > >>>>>>>>>>>>> forwarding of this communication is strictly prohibited. If > you > >>>>>>> have > >>>>>>>>>>>>> received this communication in error, please contact the > sender > >>>>>>>>>>>> immediately > >>>>>>>>>>>>> and delete it from your system. Thank You. > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> -- > >>>>>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>>>>> NOTICE: This message is intended for the use of the individual > or > >>>>>>>> entity > >>>>>>>>>> to > >>>>>>>>>>> which it is addressed and may contain information that is > >>>>>>> confidential, > >>>>>>>>>>> privileged and exempt from disclosure under applicable law. If > >> the > >>>>>>>> reader > >>>>>>>>>>> of this message is not the intended recipient, you are hereby > >>>>>>> notified > >>>>>>>>>> that > >>>>>>>>>>> any printing, copying, dissemination, distribution, disclosure > or > >>>>>>>>>>> forwarding of this communication is strictly prohibited. If you > >>>> have > >>>>>>>>>>> received this communication in error, please contact the sender > >>>>>>>>>> immediately > >>>>>>>>>>> and delete it from your system. Thank You. > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> -- > >>>>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>>>> NOTICE: This message is intended for the use of the individual > or > >>>>>>>> entity to > >>>>>>>>>> which it is addressed and may contain information that is > >>>>>>> confidential, > >>>>>>>>>> privileged and exempt from disclosure under applicable law. If > the > >>>>>>>> reader > >>>>>>>>>> of this message is not the intended recipient, you are hereby > >>>> notified > >>>>>>>> that > >>>>>>>>>> any printing, copying, dissemination, distribution, disclosure > or > >>>>>>>>>> forwarding of this communication is strictly prohibited. If you > >> have > >>>>>>>>>> received this communication in error, please contact the sender > >>>>>>>> immediately > >>>>>>>>>> and delete it from your system. Thank You. > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>>> NOTICE: This message is intended for the use of the individual or > >>>>>>> entity > >>>>>>>> to > >>>>>>>>> which it is addressed and may contain information that is > >>>> confidential, > >>>>>>>>> privileged and exempt from disclosure under applicable law. If > the > >>>>>>> reader > >>>>>>>>> of this message is not the intended recipient, you are hereby > >>>> notified > >>>>>>>> that > >>>>>>>>> any printing, copying, dissemination, distribution, disclosure or > >>>>>>>>> forwarding of this communication is strictly prohibited. If you > >> have > >>>>>>>>> received this communication in error, please contact the sender > >>>>>>>> immediately > >>>>>>>>> and delete it from your system. Thank You. > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> CONFIDENTIALITY NOTICE > >>>>>>>> NOTICE: This message is intended for the use of the individual or > >>>> entity > >>>>>>> to > >>>>>>>> which it is addressed and may contain information that is > >>>> confidential, > >>>>>>>> privileged and exempt from disclosure under applicable law. If the > >>>> reader > >>>>>>>> of this message is not the intended recipient, you are hereby > >> notified > >>>>>>> that > >>>>>>>> any printing, copying, dissemination, distribution, disclosure or > >>>>>>>> forwarding of this communication is strictly prohibited. If you > have > >>>>>>>> received this communication in error, please contact the sender > >>>>>>> immediately > >>>>>>>> and delete it from your system. Thank You. > >>>>>>>> > >>>>>>> > >>>>>> > >>>>>> -- > >>>>>> CONFIDENTIALITY NOTICE > >>>>>> NOTICE: This message is intended for the use of the individual or > >>>> entity to > >>>>>> which it is addressed and may contain information that is > >> confidential, > >>>>>> privileged and exempt from disclosure under applicable law. If the > >>>> reader > >>>>>> of this message is not the intended recipient, you are hereby > notified > >>>> that > >>>>>> any printing, copying, dissemination, distribution, disclosure or > >>>>>> forwarding of this communication is strictly prohibited. If you have > >>>>>> received this communication in error, please contact the sender > >>>> immediately > >>>>>> and delete it from your system. Thank You. > >>>>> > >>>>> > >>>>> -- > >>>>> CONFIDENTIALITY NOTICE > >>>>> NOTICE: This message is intended for the use of the individual or > >> entity > >>>> to > >>>>> which it is addressed and may contain information that is > confidential, > >>>>> privileged and exempt from disclosure under applicable law. If the > >> reader > >>>>> of this message is not the intended recipient, you are hereby > notified > >>>> that > >>>>> any printing, copying, dissemination, distribution, disclosure or > >>>>> forwarding of this communication is strictly prohibited. If you have > >>>>> received this communication in error, please contact the sender > >>>> immediately > >>>>> and delete it from your system. Thank You. > >>>> > >>>> > >>>> -- > >>>> CONFIDENTIALITY NOTICE > >>>> NOTICE: This message is intended for the use of the individual or > >> entity to > >>>> which it is addressed and may contain information that is > confidential, > >>>> privileged and exempt from disclosure under applicable law. If the > >> reader > >>>> of this message is not the intended recipient, you are hereby notified > >> that > >>>> any printing, copying, dissemination, distribution, disclosure or > >>>> forwarding of this communication is strictly prohibited. If you have > >>>> received this communication in error, please contact the sender > >> immediately > >>>> and delete it from your system. Thank You. > >>>> > >> > >> > >> -- > >> CONFIDENTIALITY NOTICE > >> NOTICE: This message is intended for the use of the individual or > entity to > >> which it is addressed and may contain information that is confidential, > >> privileged and exempt from disclosure under applicable law. If the > reader > >> of this message is not the intended recipient, you are hereby notified > that > >> any printing, copying, dissemination, distribution, disclosure or > >> forwarding of this communication is strictly prohibited. If you have > >> received this communication in error, please contact the sender > immediately > >> and delete it from your system. Thank You. > >> > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
