smallyao opened a new pull request, #1159:
URL: https://github.com/apache/bigtop/pull/1159

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'BIGTOP-3638: Your PR title ...'.
   -->
   
   ### Description of PR
   Append suffix to phoenix rpm package name
   
   ### How was this patch tested?
   1 Run './gradlew phoenix-clean phoenix-pkg -PparentDir=/usr/bigtop 
-PpkgSuffix '
   2 rpm -qpi build/phoenix/rpm/RPMS/noarch/phoenix_3_3_0-5.1.2-1.el7.noarch.rpm
   `Name        : phoenix_3_3_0
   Version     : 5.1.2
   Release     : 1.el7
   Architecture: noarch
   Install Date: (not installed)
   Group       : Development/Libraries
   Size        : 245557729
   License     : ASL 2.0
   Signature   : (none)
   Source RPM  : phoenix_3_3_0-5.1.2-1.el7.src.rpm
   Build Date  : Thu 03 Aug 2023 08:45:55 PM CST
   Build Host  : hecs-161106
   Relocations : (not relocatable)
   URL         : http://phoenix.apache.org
   Summary     : Phoenix is a SQL skin over HBase and client-embedded JDBC 
driver.
   Description :
   Phoenix is a SQL skin over HBase, delivered as a client-embedded JDBC driver.
   The Phoenix query engine transforms an SQL query into one or more HBase 
scans,
   and orchestrates their execution to produce standard JDBC result sets. Direct
   use of the HBase API, along with coprocessors and custom filters, results in
   performance on the order of milliseconds for small queries, or seconds for
   tens of millions of rows. Applications interact with Phoenix through a
   standard JDBC interface; all the usual interfaces are supported.`
   3 rpm -qpl build/phoenix/rpm/RPMS/noarch/phoenix_3_3_0-5.1.2-1.el7.noarch.rpm
   `/etc/phoenix/conf.dist
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/argparse-1.4.0
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/argparse-1.4.0/argparse.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/daemon.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/end2endTest.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/hadoop-metrics2-hbase.properties
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/hadoop-metrics2-phoenix.properties
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/hbase-omid-client-config.yml
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/hbase-site.xml
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/log4j.properties
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/performance.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/pherf-standalone.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/phoenix_utils.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/psql.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/readme.txt
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/sqlline.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/bin/traceserver.py
   /usr/bigtop/3.3.0/usr/lib/phoenix/examples
   /usr/bigtop/3.3.0/usr/lib/phoenix/examples/STOCK_SYMBOL.csv
   /usr/bigtop/3.3.0/usr/lib/phoenix/examples/STOCK_SYMBOL.sql
   /usr/bigtop/3.3.0/usr/lib/phoenix/examples/WEB_STAT.csv
   /usr/bigtop/3.3.0/usr/lib/phoenix/examples/WEB_STAT.sql
   /usr/bigtop/3.3.0/usr/lib/phoenix/examples/WEB_STAT_QUERIES.sql
   /usr/bigtop/3.3.0/usr/lib/phoenix/phoenix-client-hbase-2.4-5.1.2.jar
   /usr/bigtop/3.3.0/usr/lib/phoenix/phoenix-client.jar
   /usr/bigtop/3.3.0/usr/lib/phoenix/phoenix-pherf-5.1.2.jar
   /usr/bigtop/3.3.0/usr/lib/phoenix/phoenix-server-hbase-2.4-5.1.2.jar
   /usr/bigtop/3.3.0/usr/lib/phoenix/phoenix-server.jar`
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'BIGTOP-3638. Your PR title ...')?
   - [ ] Make sure that newly added files do not have any licensing issues. 
When in doubt refer to https://www.apache.org/licenses/


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to