Help in development of recommendation engine.
Hello Sir, I am an engineering student and passionate about Hadoop and such kind of technology. I am developing a recommendation system using phoenix which uses the data from stack exchange dump and will recommend the list of users who can possibly answer a question asked on sites like stack overflow in a best possible way depending upon the upvotes on their previous answers and recent activities etc. This list will be used by the person who seeks answer to directly interact with the person having good expertise on that specific skill. It would enable them to have a one to one interaction and hence knowledge will flow smoothly from upper tier to lower tier. I request you to kindly help me designing the architecture for that and any valuable suggestions are cordially invited. Thanks in advance. Abhishek Srivastava abhishekkuma...@somaiya.edu Sent from Mail for Windows 10
[jira] [Commented] (PHOENIX-2238) Bulk dataload Hive data with \001 delimiter
[ https://issues.apache.org/jira/browse/PHOENIX-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738953#comment-14738953 ] ASF GitHub Bot commented on PHOENIX-2238: - Github user gabrielreid commented on the pull request: https://github.com/apache/phoenix/pull/116#issuecomment-139287029 I think that this is an interesting idea, but did you see my comment on [PHOENIX-2238](https://issues.apache.org/jira/browse/PHOENIX-2238)? There is support built in to the shell which allows you to supply non-printable characters. I can see how this might be more user-friendly for some, while being confusing for others (who are already familiar with the standard method of providing non-printable characters on the command line). Another concern that I have is that providing these kinds of literals that start with backslashes also require some understanding about the rules of escaping when supplying command line parameters, so this kind of makes me think that it might be better to go completely for expecting users to know how to work with the shell properly. What do you think? > Bulk dataload Hive data with \001 delimiter > --- > > Key: PHOENIX-2238 > URL: https://issues.apache.org/jira/browse/PHOENIX-2238 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.3.0 >Reporter: q79969786 > > Bulk dataload : > hadoop jar > /opt/cloudera/parcels/CLABS_PHOENIX-4.3.0-1.clabs_phoenix1.0.0.p0.78/lib/phoenix/phoenix-4.3.0-clabs-phoenix-1.0.0-client.jar > org.apache.phoenix.mapreduce.CsvBulkLoadTool --table test_phoenix_import > --zookeeper n1,n2,n3 --delimiter \001 --input /user/wym/test_phoenix_import > The path ‘/user/wym/test_phoenix_import’ is a directory contains Hive data, > so the default delimiter is \001. > Exception: > 15/09/08 15:22:17 INFO zookeeper.ClientCnxn: EventThread shut down > 15/09/08 15:22:17 INFO zookeeper.ZooKeeper: Session: 0x34f1c9be8ba5667 closed > Exception in thread "main" java.lang.IllegalArgumentException: Illegal > delimiter character: 001 > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.configureOptions(CsvBulkLoadTool.java:327) > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.loadData(CsvBulkLoadTool.java:201) > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.run(CsvBulkLoadTool.java:186) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.main(CsvBulkLoadTool.java:97) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.hadoop.util.RunJar.run(RunJar.java:221) > at org.apache.hadoop.util.RunJar.main(RunJar.java:136) > 15/09/08 15:22:18 INFO client.ConnectionManager$HConnectionImplementation: > Closing zookeeper sessionid=0x34f1c9be8ba5665 > 15/09/08 15:22:18 INFO zookeeper.ClientCnxn: EventThread shut down > 15/09/08 15:22:18 INFO zookeeper.ZooKeeper: Session: 0x34f1c9be8ba5665 closed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] phoenix pull request: PHOENIX-2238 Support more delimiter when usi...
Github user gabrielreid commented on the pull request: https://github.com/apache/phoenix/pull/116#issuecomment-139287029 I think that this is an interesting idea, but did you see my comment on [PHOENIX-2238](https://issues.apache.org/jira/browse/PHOENIX-2238)? There is support built in to the shell which allows you to supply non-printable characters. I can see how this might be more user-friendly for some, while being confusing for others (who are already familiar with the standard method of providing non-printable characters on the command line). Another concern that I have is that providing these kinds of literals that start with backslashes also require some understanding about the rules of escaping when supplying command line parameters, so this kind of makes me think that it might be better to go completely for expecting users to know how to work with the shell properly. What do you think? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (PHOENIX-2244) fix rat violations
[
https://issues.apache.org/jira/browse/PHOENIX-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739127#comment-14739127
]
Nishani commented on PHOENIX-2244:
---
Hi,
Is it ok to update the respective PRs?
Thanks.
> fix rat violations
> --
>
> Key: PHOENIX-2244
> URL: https://issues.apache.org/jira/browse/PHOENIX-2244
> Project: Phoenix
> Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nishani
>Priority: Blocker
> Fix For: 4.6.0
>
>
> We'll need to resolve the licensing header violations introduced here before
> we can release.
> {noformat}
> *
> Summary
> ---
> Generated at: 2015-09-09T16:45:47-07:00
> Notes: 0
> Binaries: 9
> Archives: 1
> Standards: 53
> Apache Licensed: 9
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 44 Unknown Licenses
> ***
> Unapproved licenses:
> src/main/webapp/css/bootstrap-theme.css
> src/main/webapp/css/bootstrap-theme.css.map
> src/main/webapp/css/bootstrap.css
> src/main/webapp/css/bootstrap.css.map
> src/main/webapp/css/font-awesome.css
> src/main/webapp/fonts/fontawesome-webfont.svg
> src/main/webapp/fonts/glyphicons-halflings-regular.svg
> src/main/webapp/index.html
> src/main/webapp/js/api/chart-model.js
> src/main/webapp/js/app.js
> src/main/webapp/js/config/chart-config.js
> src/main/webapp/js/controllers/accordion-controllers.js
> src/main/webapp/js/controllers/dependency-tree-controllers.js
> src/main/webapp/js/controllers/list-controllers.js
> src/main/webapp/js/controllers/search-controllers.js
> src/main/webapp/js/controllers/timeline-controllers.js
> src/main/webapp/js/controllers/trace-count-controllers.js
> src/main/webapp/js/controllers/trace-distribution-controllers.js
> src/main/webapp/js/factories/statement-factory-config.js
> src/main/webapp/js/factories/statement-factory.js
> src/main/webapp/js/lib/angular-mocks.js
> src/main/webapp/js/lib/angular-route.js
> src/main/webapp/js/lib/angular.js
> src/main/webapp/js/lib/bootstrap.js
> src/main/webapp/js/lib/jquery-2.1.4.js
> src/main/webapp/js/lib/jquery.min.js
> src/main/webapp/js/lib/ng-google-chart.js
> src/main/webapp/js/lib/ui-bootstrap-tpls.js
> src/main/webapp/js/services/generate-statement-service.js
> src/main/webapp/partials/about.html
> src/main/webapp/partials/chart.html
> src/main/webapp/partials/contact.html
> src/main/webapp/partials/dependency-tree.html
> src/main/webapp/partials/google-chart.html
> src/main/webapp/partials/help.html
> src/main/webapp/partials/home.html
> src/main/webapp/partials/list.html
> src/main/webapp/partials/phoenix-trace.html
> src/main/webapp/partials/search.html
> src/main/webapp/WEB-INF/web.xml
> src/test/webapp/js/specs/app-route-spec.js
> src/test/webapp/js/specs/timeline-ctrl-spec.js
> src/test/webapp/js/specs/trace-list-ctrl-spec.js
> src/test/webapp/js/specs/tracing-app-ctrl-spec.js
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2245) phoenix-4.5.1-HBase-1.0 build fails for hadoop2
[
https://issues.apache.org/jira/browse/PHOENIX-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mujtaba Chohan resolved PHOENIX-2245.
-
Resolution: Not A Problem
Phoenix builds are not hadoop profile based for a while so there is no need to
specify -Dhadoop.profile=2. They are built against Hadoop2 by default and also
HBase has dropped support for Hadoop1x as well.
> phoenix-4.5.1-HBase-1.0 build fails for hadoop2
> ---
>
> Key: PHOENIX-2245
> URL: https://issues.apache.org/jira/browse/PHOENIX-2245
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.4.0, 4.5.1
>Reporter: alex kamil
>
> it fails when -Dhadoop.profile=2 is set but compiles ok otherwise for both
> 4.4.0 and 4.5.1
> wget
> http://mirror.nexcess.net/apache/phoenix/phoenix-4.5.1-HBase-1.0/src/phoenix-4.5.1-HBase-1.0-src.tar.gz
> tar xvzf phoenix-4.5.1-HBase-1.0-src.tar.gz
> cd phoenix-4.5.1-HBase-1.0-src
> mvn package -DskipTests -Dhadoop.profile=2
>
> [WARNING] The POM for org.apache.hbase:hbase-testing-util:jar:1.0.1 is
> invalid, transitive dependencies (if any) will not be available: 4 problems
> were encountered while building the effective model for or
> [ERROR] 'dependencies.dependency.artifactId' for
> org.apache.hbase:${compat.module}:jar with value '${compat.module}' does not
> match a valid id pattern. @
> [ERROR] 'dependencies.dependency.artifactId' for
> org.apache.hbase:${compat.module}:test-jar with value '${compat.module}' does
> not match a valid id pattern. @
> [ERROR] 'dependencyManagement.dependencies.dependency.artifactId' for
> org.apache.hbase:${compat.module}:jar with value '${compat.module}' does not
> match a valid id pattern. @
> [ERROR] 'dependencyManagement.dependencies.dependency.artifactId' for
> org.apache.hbase:${compat.module}:test-jar with value '${compat.module}' does
> not match a valid id pattern. @
> ...
> [WARNING] Invalid POM for org.apache.hbase:hbase-testing-util:jar:1.0.1,
> transitive dependencies (if any) will not be available, enable debug logging
> for more details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-it:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-it:test-jar:tests:1.0.1,
> transitive dependencies (if any) will not be available, enable debug logging
> for more details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-common:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-common:jar:1.0.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-protocol:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-protocol:jar:1.0.1,
> transitive dependencies (if any) will not be available, enable debug logging
> for more details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-client:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-client:jar:1.0.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-server:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-server:jar:1.0.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-server:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-server:test-jar:tests:1.0.1,
> transitive dependencies (if any) will not be available, enable debug logging
> for more details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-hadoop-compat:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-hadoop-compat:jar:1.0.1,
> transitive dependencies (if any) will not be available, enable debug logging
> for more details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-hadoop-compat:jar:1.0.1
> [WARNING] Invalid POM for
> org.apache.hbase:hbase-hadoop-compat:test-jar:tests:1.0.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-hadoop2-compat:jar:1.0.1
> [WARNING] Invalid POM for org.apache.hbase:hbase-hadoop2-compat:jar:1.0.1,
> transitive dependencies (if any) will not be available, enable debug logging
> for more details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-hadoop2-compat:jar:1.0.1
> [WARNING] Invalid POM for
> org.apache.hbase:hbase-hadoop2-compat:test-jar:tests:1.0.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] Failed to build parent project for
> org.apache.hbase:hbase-server:
[jira] [Commented] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App
[ https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739220#comment-14739220 ] Mujtaba Chohan commented on PHOENIX-2186: - Looks good for initial/beta commit. > Creating backend services for the Phoenix Tracing Web App > - > > Key: PHOENIX-2186 > URL: https://issues.apache.org/jira/browse/PHOENIX-2186 > Project: Phoenix > Issue Type: Sub-task >Reporter: Nishani >Assignee: Nishani > Labels: Tracing > Fix For: 4.6.0 > > Attachments: 2186-master.patch > > > This will include the following components. > Main class > Pom file > Launch script > Backend trace service API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2204) Add correlate UNNEST test cases
[ https://issues.apache.org/jira/browse/PHOENIX-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-2204. -- Resolution: Fixed > Add correlate UNNEST test cases > --- > > Key: PHOENIX-2204 > URL: https://issues.apache.org/jira/browse/PHOENIX-2204 > Project: Phoenix > Issue Type: Sub-task >Reporter: Maryann Xue >Assignee: Maryann Xue > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2226) Support Semi-Join in Phoenix/Calcite Integration
[ https://issues.apache.org/jira/browse/PHOENIX-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-2226. -- Resolution: Fixed > Support Semi-Join in Phoenix/Calcite Integration > > > Key: PHOENIX-2226 > URL: https://issues.apache.org/jira/browse/PHOENIX-2226 > Project: Phoenix > Issue Type: Task >Reporter: Maryann Xue >Assignee: Maryann Xue > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2225) Support Correlate (Nested-loop Join) in Phoenix/Calcite Integration
[ https://issues.apache.org/jira/browse/PHOENIX-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-2225. -- Resolution: Fixed > Support Correlate (Nested-loop Join) in Phoenix/Calcite Integration > --- > > Key: PHOENIX-2225 > URL: https://issues.apache.org/jira/browse/PHOENIX-2225 > Project: Phoenix > Issue Type: Task >Reporter: Maryann Xue >Assignee: Maryann Xue > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
alex kamil created PHOENIX-2246: --- Summary: error “object spark is not a member of package org.apache.phoenix" Key: PHOENIX-2246 URL: https://issues.apache.org/jira/browse/PHOENIX-2246 Project: Phoenix Issue Type: Bug Reporter: alex kamil Priority: Minor phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark jar, so after adding phoenix client jar on spark classpath getting " error “object spark is not a member of package org.apache.phoenix" in spark shell pls add phoenix spark jar to the binaries and also add to documentation that phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[ https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] alex kamil updated PHOENIX-2246: Affects Version/s: 4.5.1 > error “object spark is not a member of package org.apache.phoenix" > -- > > Key: PHOENIX-2246 > URL: https://issues.apache.org/jira/browse/PHOENIX-2246 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.5.1 >Reporter: alex kamil >Priority: Minor > > phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark > jar, > so after adding phoenix client jar on spark classpath getting " error “object > spark is not a member of package org.apache.phoenix" in spark shell > pls add phoenix spark jar to the binaries and also add to documentation that > phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[ https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] alex kamil updated PHOENIX-2246: Description: phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark jar, so after adding phoenix client jar on spark classpath getting " error “object spark is not a member of package org.apache.phoenix" in spark shell the solution was to compile phoenix from source and add phoenix-spark jar pls add phoenix spark jar to the binaries and also add to documentation that phoenix-spark jar is required on the spark classpath was: phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark jar, so after adding phoenix client jar on spark classpath getting " error “object spark is not a member of package org.apache.phoenix" in spark shell pls add phoenix spark jar to the binaries and also add to documentation that phoenix-spark jar is required on the spark classpath > error “object spark is not a member of package org.apache.phoenix" > -- > > Key: PHOENIX-2246 > URL: https://issues.apache.org/jira/browse/PHOENIX-2246 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.5.1 >Reporter: alex kamil >Priority: Minor > > phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark > jar, > so after adding phoenix client jar on spark classpath getting " error “object > spark is not a member of package org.apache.phoenix" in spark shell > the solution was to compile phoenix from source and add phoenix-spark jar > pls add phoenix spark jar to the binaries and also add to documentation that > phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[ https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] alex kamil updated PHOENIX-2246: Description: phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark jar, so after adding phoenix client jar on spark classpath getting " error “object spark is not a member of package org.apache.phoenix" in spark shell the solution was to build phoenix from source and add phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar to SPARK_CLASSPATH in spark-env.sh pls add phoenix spark jar to the binaries distribution and also add to documentation that phoenix-spark jar is required on the spark classpath was: phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark jar, so after adding phoenix client jar on spark classpath getting " error “object spark is not a member of package org.apache.phoenix" in spark shell the solution was to compile phoenix from source and add phoenix-spark jar pls add phoenix spark jar to the binaries and also add to documentation that phoenix-spark jar is required on the spark classpath > error “object spark is not a member of package org.apache.phoenix" > -- > > Key: PHOENIX-2246 > URL: https://issues.apache.org/jira/browse/PHOENIX-2246 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.5.1 >Reporter: alex kamil >Priority: Minor > > phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark > jar, > so after adding phoenix client jar on spark classpath getting " error “object > spark is not a member of package org.apache.phoenix" in spark shell > the solution was to build phoenix from source and add > phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar > to SPARK_CLASSPATH in spark-env.sh > pls add phoenix spark jar to the binaries distribution and also add to > documentation that phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App
[ https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739296#comment-14739296 ] Nick Dimiduk commented on PHOENIX-2186: --- [~jamestaylor] looks like [~nishani] opened PHOENIX-2190 for documentation. > Creating backend services for the Phoenix Tracing Web App > - > > Key: PHOENIX-2186 > URL: https://issues.apache.org/jira/browse/PHOENIX-2186 > Project: Phoenix > Issue Type: Sub-task >Reporter: Nishani >Assignee: Nishani > Labels: Tracing > Fix For: 4.6.0 > > Attachments: 2186-master.patch > > > This will include the following components. > Main class > Pom file > Launch script > Backend trace service API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[ https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739331#comment-14739331 ] James Taylor commented on PHOENIX-2246: --- [~jmahonin] - we're getting ready to put out a 4.5.2 patch RC. I seem to remember you committing something that made our Spark integration as part of the phoenix-client jar, no? > error “object spark is not a member of package org.apache.phoenix" > -- > > Key: PHOENIX-2246 > URL: https://issues.apache.org/jira/browse/PHOENIX-2246 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.5.1 >Reporter: alex kamil >Priority: Minor > > phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark > jar, > so after adding phoenix client jar on spark classpath getting " error “object > spark is not a member of package org.apache.phoenix" in spark shell > the solution was to build phoenix from source and add > phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar > to SPARK_CLASSPATH in spark-env.sh > pls add phoenix spark jar to the binaries distribution and also add to > documentation that phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[
https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739335#comment-14739335
]
Josh Mahonin commented on PHOENIX-2246:
---
Taking a look at the phoenix-4.5.1-HBase-1.0-client.jar I do see that the
phoenix-spark dependencies are included:
{noformat}
$ jar tvf phoenix-4.5.1-HBase-1.0-client.jar | grep spark | head
0 Fri Aug 14 16:20:02 EDT 2015 org/apache/phoenix/spark/
1778 Fri Aug 14 16:20:02 EDT 2015 org/apache/phoenix/spark/package.class
1721 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/SparkContextFunctions$$anonfun$phoenixTableAsRDD$1.class
6597 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/DataFrameFunctions.class
3076 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/ProductRDDFunctions$$anonfun$1.class
1294 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/PhoenixRDD$$anonfun$1.class
1783 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/PhoenixRelation$.class
3196 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/DataFrameFunctions$$anonfun$1.class
5995 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/PhoenixRecordWritable.class
3404 Fri Aug 14 16:20:02 EDT 2015
org/apache/phoenix/spark/SparkContextFunctions.class
{noformat}
I'm in transit, so can't verify full functionality with spark-shell at the
moment. Can you verify that you are using the correct JAR and SPARK_CLASSPATH
settings are correct?
> error “object spark is not a member of package org.apache.phoenix"
> --
>
> Key: PHOENIX-2246
> URL: https://issues.apache.org/jira/browse/PHOENIX-2246
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.5.1
>Reporter: alex kamil
>Priority: Minor
>
> phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark
> jar,
> so after adding phoenix client jar on spark classpath getting " error “object
> spark is not a member of package org.apache.phoenix" in spark shell
> the solution was to build phoenix from source and add
> phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar
> to SPARK_CLASSPATH in spark-env.sh
> pls add phoenix spark jar to the binaries distribution and also add to
> documentation that phoenix-spark jar is required on the spark classpath
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information
[ https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated PHOENIX-1118: -- Fix Version/s: 4.6.0 > Provide a tool for visualizing Phoenix tracing information > -- > > Key: PHOENIX-1118 > URL: https://issues.apache.org/jira/browse/PHOENIX-1118 > Project: Phoenix > Issue Type: New Feature >Reporter: James Taylor >Assignee: Nishani > Labels: Java, SQL, Visualization, gsoc2015, mentor > Fix For: 4.6.0 > > Attachments: MockUp1-TimeSlider.png, MockUp2-AdvanceSearch.png, > MockUp3-PatternDetector.png, MockUp4-FlameGraph.png, Screenshot of dependency > tree.png, Screenshot-loading-trace-list.png, m1-mockUI-tracedistribution.png, > m1-mockUI-tracetimeline.png, screenshot of tracing timeline.png, screenshot > of tracing web app.png, timeline.png > > > Currently there's no means of visualizing the trace information provided by > Phoenix. We should provide some simple charting over our metrics tables. Take > a look at the following JIRA for sample queries: > https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14323151&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151 > The tool need to provide visualization over SYSTEM.TRACING_STATS table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[ https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739347#comment-14739347 ] Josh Mahonin commented on PHOENIX-2246: --- [~jamestaylor] Very briefly between releases, phoenix-spark had been removed from the client assembly pom due to the size of the dependencies it was pulling in. The relevant commit which fixed that is here, and I believe was included in 4.5.0: https://github.com/apache/phoenix/commit/b61ef77e509a024ccaf6c3ce74c385c31c5f534a The 4.5.1 client JAR I just downloaded has those classes available, and I don't see any relevant changes since 4.5.0 (which I use myself) so I think that should be OK. However, I can't 100% confirm till late tonight or tomorrow. > error “object spark is not a member of package org.apache.phoenix" > -- > > Key: PHOENIX-2246 > URL: https://issues.apache.org/jira/browse/PHOENIX-2246 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.5.1 >Reporter: alex kamil >Priority: Minor > > phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark > jar, > so after adding phoenix client jar on spark classpath getting " error “object > spark is not a member of package org.apache.phoenix" in spark shell > the solution was to build phoenix from source and add > phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar > to SPARK_CLASSPATH in spark-env.sh > pls add phoenix spark jar to the binaries distribution and also add to > documentation that phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2190) Update docs for Trace Visualization
[ https://issues.apache.org/jira/browse/PHOENIX-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated PHOENIX-2190: -- Summary: Update docs for Trace Visualization (was: Updating the Documentation) > Update docs for Trace Visualization > --- > > Key: PHOENIX-2190 > URL: https://issues.apache.org/jira/browse/PHOENIX-2190 > Project: Phoenix > Issue Type: Sub-task >Reporter: Nishani >Assignee: Nishani > Attachments: Screenshot-trace-web-doc1.png, > Screenshot-trace-web-doc2.png, Screenshot-trace-web-doc3.png, > phoenix-trace-web-app-doc.patch, trace-images.zip > > > The Documentation would contain the following. > How to start the Tracing Web Application > How to change the port number on which it runs > Five visualization features in the Tracing Web Application -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2190) Update docs for Trace Visualization
[ https://issues.apache.org/jira/browse/PHOENIX-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated PHOENIX-2190: -- Fix Version/s: 4.6.0 > Update docs for Trace Visualization > --- > > Key: PHOENIX-2190 > URL: https://issues.apache.org/jira/browse/PHOENIX-2190 > Project: Phoenix > Issue Type: Sub-task >Reporter: Nishani >Assignee: Nishani > Fix For: 4.6.0 > > Attachments: Screenshot-trace-web-doc1.png, > Screenshot-trace-web-doc2.png, Screenshot-trace-web-doc3.png, > phoenix-trace-web-app-doc.patch, trace-images.zip > > > The Documentation would contain the following. > How to start the Tracing Web Application > How to change the port number on which it runs > Five visualization features in the Tracing Web Application -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2244) fix rat violations
[
https://issues.apache.org/jira/browse/PHOENIX-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739366#comment-14739366
]
Nick Dimiduk commented on PHOENIX-2244:
---
All the other code is now on master. Please provide a patch based on master and
I'll make sure it's applied to the active 4.x branches on commit.
> fix rat violations
> --
>
> Key: PHOENIX-2244
> URL: https://issues.apache.org/jira/browse/PHOENIX-2244
> Project: Phoenix
> Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nishani
>Priority: Blocker
> Fix For: 4.6.0
>
>
> We'll need to resolve the licensing header violations introduced here before
> we can release.
> {noformat}
> *
> Summary
> ---
> Generated at: 2015-09-09T16:45:47-07:00
> Notes: 0
> Binaries: 9
> Archives: 1
> Standards: 53
> Apache Licensed: 9
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 44 Unknown Licenses
> ***
> Unapproved licenses:
> src/main/webapp/css/bootstrap-theme.css
> src/main/webapp/css/bootstrap-theme.css.map
> src/main/webapp/css/bootstrap.css
> src/main/webapp/css/bootstrap.css.map
> src/main/webapp/css/font-awesome.css
> src/main/webapp/fonts/fontawesome-webfont.svg
> src/main/webapp/fonts/glyphicons-halflings-regular.svg
> src/main/webapp/index.html
> src/main/webapp/js/api/chart-model.js
> src/main/webapp/js/app.js
> src/main/webapp/js/config/chart-config.js
> src/main/webapp/js/controllers/accordion-controllers.js
> src/main/webapp/js/controllers/dependency-tree-controllers.js
> src/main/webapp/js/controllers/list-controllers.js
> src/main/webapp/js/controllers/search-controllers.js
> src/main/webapp/js/controllers/timeline-controllers.js
> src/main/webapp/js/controllers/trace-count-controllers.js
> src/main/webapp/js/controllers/trace-distribution-controllers.js
> src/main/webapp/js/factories/statement-factory-config.js
> src/main/webapp/js/factories/statement-factory.js
> src/main/webapp/js/lib/angular-mocks.js
> src/main/webapp/js/lib/angular-route.js
> src/main/webapp/js/lib/angular.js
> src/main/webapp/js/lib/bootstrap.js
> src/main/webapp/js/lib/jquery-2.1.4.js
> src/main/webapp/js/lib/jquery.min.js
> src/main/webapp/js/lib/ng-google-chart.js
> src/main/webapp/js/lib/ui-bootstrap-tpls.js
> src/main/webapp/js/services/generate-statement-service.js
> src/main/webapp/partials/about.html
> src/main/webapp/partials/chart.html
> src/main/webapp/partials/contact.html
> src/main/webapp/partials/dependency-tree.html
> src/main/webapp/partials/google-chart.html
> src/main/webapp/partials/help.html
> src/main/webapp/partials/home.html
> src/main/webapp/partials/list.html
> src/main/webapp/partials/phoenix-trace.html
> src/main/webapp/partials/search.html
> src/main/webapp/WEB-INF/web.xml
> src/test/webapp/js/specs/app-route-spec.js
> src/test/webapp/js/specs/timeline-ctrl-spec.js
> src/test/webapp/js/specs/trace-list-ctrl-spec.js
> src/test/webapp/js/specs/tracing-app-ctrl-spec.js
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (PHOENIX-2247) Fix rat violations in Pherf
Nick Dimiduk created PHOENIX-2247:
-
Summary: Fix rat violations in Pherf
Key: PHOENIX-2247
URL: https://issues.apache.org/jira/browse/PHOENIX-2247
Project: Phoenix
Issue Type: Task
Reporter: Nick Dimiduk
Priority: Blocker
Fix For: 4.6.0
Over on PHOENIX-2244, I noticed violations in Pherf as well.
{noformat}
Unapproved licenses:
src/test/resources/datamodel/test_schema_mt_view.sql
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[ https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739376#comment-14739376 ] alex kamil commented on PHOENIX-2246: - my bad, included server jar instead of client, I do see spark classes in phoenix client and it works without phoenix-spark jar > error “object spark is not a member of package org.apache.phoenix" > -- > > Key: PHOENIX-2246 > URL: https://issues.apache.org/jira/browse/PHOENIX-2246 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.5.1 >Reporter: alex kamil >Priority: Minor > > phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark > jar, > so after adding phoenix client jar on spark classpath getting " error “object > spark is not a member of package org.apache.phoenix" in spark shell > the solution was to build phoenix from source and add > phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar > to SPARK_CLASSPATH in spark-env.sh > pls add phoenix spark jar to the binaries distribution and also add to > documentation that phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[ https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] alex kamil resolved PHOENIX-2246. - Resolution: Not A Problem > error “object spark is not a member of package org.apache.phoenix" > -- > > Key: PHOENIX-2246 > URL: https://issues.apache.org/jira/browse/PHOENIX-2246 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.5.1 >Reporter: alex kamil >Priority: Minor > > phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark > jar, > so after adding phoenix client jar on spark classpath getting " error “object > spark is not a member of package org.apache.phoenix" in spark shell > the solution was to build phoenix from source and add > phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar > to SPARK_CLASSPATH in spark-env.sh > pls add phoenix spark jar to the binaries distribution and also add to > documentation that phoenix-spark jar is required on the spark classpath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[
https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739387#comment-14739387
]
Josh Mahonin commented on PHOENIX-2246:
---
I tracked down a machine that had 4.5.1-HBase-0.98 on it. I'm able to load the
phoenix-spark dependencies from spark-shell without issue.
For reference, my spark-env.sh:
{{ SPARK_CLASSPATH=/opt/interset/spark/lib/phoenix-client-4.5.1-HBase-0.98.jar
}}
> error “object spark is not a member of package org.apache.phoenix"
> --
>
> Key: PHOENIX-2246
> URL: https://issues.apache.org/jira/browse/PHOENIX-2246
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.5.1
>Reporter: alex kamil
>Priority: Minor
>
> phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark
> jar,
> so after adding phoenix client jar on spark classpath getting " error “object
> spark is not a member of package org.apache.phoenix" in spark shell
> the solution was to build phoenix from source and add
> phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar
> to SPARK_CLASSPATH in spark-env.sh
> pls add phoenix spark jar to the binaries distribution and also add to
> documentation that phoenix-spark jar is required on the spark classpath
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (PHOENIX-2246) error “object spark is not a member of package org.apache.phoenix"
[
https://issues.apache.org/jira/browse/PHOENIX-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739387#comment-14739387
]
Josh Mahonin edited comment on PHOENIX-2246 at 9/10/15 7:08 PM:
I tracked down a machine that had 4.5.1-HBase-0.98 on it. I'm able to load the
phoenix-spark dependencies from spark-shell without issue.
For reference, my spark-env.sh:
{noformat}
SPARK_CLASSPATH=/opt/interset/spark/lib/phoenix-client-4.5.1-HBase-0.98.jar
{noformat}
was (Author: jmahonin):
I tracked down a machine that had 4.5.1-HBase-0.98 on it. I'm able to load the
phoenix-spark dependencies from spark-shell without issue.
For reference, my spark-env.sh:
{{ SPARK_CLASSPATH=/opt/interset/spark/lib/phoenix-client-4.5.1-HBase-0.98.jar
}}
> error “object spark is not a member of package org.apache.phoenix"
> --
>
> Key: PHOENIX-2246
> URL: https://issues.apache.org/jira/browse/PHOENIX-2246
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.5.1
>Reporter: alex kamil
>Priority: Minor
>
> phoenix binaries (phoenix-4.5.1-HBase-1.0-bin) do not include phoenix-spark
> jar,
> so after adding phoenix client jar on spark classpath getting " error “object
> spark is not a member of package org.apache.phoenix" in spark shell
> the solution was to build phoenix from source and add
> phoenix-4.5.1-HBase-1.0-src/phoenix-spark/target/phoenix-spark-4.5.1-HBase-1.0.jar
> to SPARK_CLASSPATH in spark-env.sh
> pls add phoenix spark jar to the binaries distribution and also add to
> documentation that phoenix-spark jar is required on the spark classpath
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-2247) Fix rat violations in Pherf
[
https://issues.apache.org/jira/browse/PHOENIX-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739404#comment-14739404
]
James Taylor commented on PHOENIX-2247:
---
[~mujtabachohan]
> Fix rat violations in Pherf
> ---
>
> Key: PHOENIX-2247
> URL: https://issues.apache.org/jira/browse/PHOENIX-2247
> Project: Phoenix
> Issue Type: Task
>Reporter: Nick Dimiduk
>Priority: Blocker
> Fix For: 4.6.0
>
>
> Over on PHOENIX-2244, I noticed violations in Pherf as well.
> {noformat}
> Unapproved licenses:
> src/test/resources/datamodel/test_schema_mt_view.sql
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PHOENIX-2240) Duplicate keys generated by performance.py script
[ https://issues.apache.org/jira/browse/PHOENIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739449#comment-14739449 ] James Taylor commented on PHOENIX-2240: --- +1 > Duplicate keys generated by performance.py script > - > > Key: PHOENIX-2240 > URL: https://issues.apache.org/jira/browse/PHOENIX-2240 > Project: Phoenix > Issue Type: Bug >Reporter: Mujtaba Chohan >Assignee: Mujtaba Chohan >Priority: Minor > Attachments: PHOENIX-2240.patch > > > 500 out of 100M rows are duplicate. See details at > http://search-hadoop.com/m/9UY0h26jwA21rW0i1/v=threaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2247) Fix rat violations in Pherf
[
https://issues.apache.org/jira/browse/PHOENIX-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mujtaba Chohan resolved PHOENIX-2247.
-
Resolution: Fixed
> Fix rat violations in Pherf
> ---
>
> Key: PHOENIX-2247
> URL: https://issues.apache.org/jira/browse/PHOENIX-2247
> Project: Phoenix
> Issue Type: Task
>Reporter: Nick Dimiduk
>Priority: Blocker
> Fix For: 4.6.0
>
>
> Over on PHOENIX-2244, I noticed violations in Pherf as well.
> {noformat}
> Unapproved licenses:
> src/test/resources/datamodel/test_schema_mt_view.sql
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2240) Duplicate keys generated by performance.py script
[ https://issues.apache.org/jira/browse/PHOENIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan resolved PHOENIX-2240. - Resolution: Fixed Fix Version/s: 4.5.2 4.6 > Duplicate keys generated by performance.py script > - > > Key: PHOENIX-2240 > URL: https://issues.apache.org/jira/browse/PHOENIX-2240 > Project: Phoenix > Issue Type: Bug >Reporter: Mujtaba Chohan >Assignee: Mujtaba Chohan >Priority: Minor > Fix For: 4.6, 4.5.2 > > Attachments: PHOENIX-2240.patch > > > 500 out of 100M rows are duplicate. See details at > http://search-hadoop.com/m/9UY0h26jwA21rW0i1/v=threaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2237) Optimize search comparator in KeyValyeUtil
[ https://issues.apache.org/jira/browse/PHOENIX-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2237: -- Fix Version/s: 4.5.2 > Optimize search comparator in KeyValyeUtil > -- > > Key: PHOENIX-2237 > URL: https://issues.apache.org/jira/browse/PHOENIX-2237 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 4.5.2 >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl > Fix For: 4.6, 4.5.2 > > Attachments: 2237-master.txt > > > See observation in parent: > # We are guaranteed to be passed KVs of the same row > # There'll be at most one version for each column > #1 allows us to completely avoid comparing the row keys. > #2 Let's us do exact searches for columns. Allowing us to simplify the code - > and save a bit more performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
REMINDER: please ask RM before committing to a point release branch
Quick reminder: prior to committing to a point release branch (i.e. 4.4-*, 4.5-*), please make sure to ping the release manager first: For 4.4-* ask Rajeshbabu For 4.5-* ask James Also, make sure if you commit to one of them (i.e. 4.5-HBase-0.98) that you commit to all of them (4.5-HBase-1.0 and 4.5-HBase-1.1). We want to make sure we maintain feature parity across HBase versions. Thanks, James
[jira] [Commented] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App
[ https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739592#comment-14739592 ] Hudson commented on PHOENIX-2186: - SUCCESS: Integrated in Phoenix-master #896 (See [https://builds.apache.org/job/Phoenix-master/896/]) PHOENIX-2186 Creating backend services for the Phoenix Tracing Web App (Nishani) (ndimiduk: rev 2f18fc821c6284a13de2878db27142e84b7bf9f0) * phoenix-tracing-webapp/src/main/java/org/apache/phoenix/tracingwebapp/http/EntityFactory.java * pom.xml * bin/phoenix_utils.py * phoenix-tracing-webapp/src/main/config/checkstyle/checker.xml * phoenix-tracing-webapp/README.md * phoenix-tracing-webapp/src/main/config/checkstyle/header.txt * phoenix-tracing-webapp/src/build/trace-server-runnable.xml * phoenix-tracing-webapp/src/main/config/checkstyle/suppressions.xml * phoenix-tracing-webapp/src/main/java/org/apache/phoenix/tracingwebapp/http/ConnectionFactory.java * phoenix-tracing-webapp/src/main/java/org/apache/phoenix/tracingwebapp/http/TraceServlet.java * phoenix-tracing-webapp/src/main/webapp/index.html * phoenix-tracing-webapp/src/main/webapp/WEB-INF/web.xml * phoenix-tracing-webapp/pom.xml * bin/traceserver.py * phoenix-tracing-webapp/src/main/java/org/apache/phoenix/tracingwebapp/http/Main.java > Creating backend services for the Phoenix Tracing Web App > - > > Key: PHOENIX-2186 > URL: https://issues.apache.org/jira/browse/PHOENIX-2186 > Project: Phoenix > Issue Type: Sub-task >Reporter: Nishani >Assignee: Nishani > Labels: Tracing > Fix For: 4.6.0 > > Attachments: 2186-master.patch > > > This will include the following components. > Main class > Pom file > Launch script > Backend trace service API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2187) Creating the front-end application for Phoenix Tracing Web App
[ https://issues.apache.org/jira/browse/PHOENIX-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739593#comment-14739593 ] Hudson commented on PHOENIX-2187: - SUCCESS: Integrated in Phoenix-master #896 (See [https://builds.apache.org/job/Phoenix-master/896/]) PHOENIX-2187 Creating the front-end application for Phoenix Tracing Web App (Nishani) (ndimiduk: rev f76062c90070fded2cb997ccf9232cea5603e3e8) * phoenix-tracing-webapp/src/main/webapp/js/factories/statement-factory.js * phoenix-tracing-webapp/src/main/webapp/partials/about.html * phoenix-tracing-webapp/src/main/webapp/js/lib/jquery.min.js * phoenix-tracing-webapp/src/main/webapp/fonts/glyphicons-halflings-regular.ttf * phoenix-tracing-webapp/src/main/webapp/js/controllers/trace-count-controllers.js * phoenix-tracing-webapp/src/main/webapp/fonts/glyphicons-halflings-regular.woff2 * phoenix-tracing-webapp/src/main/webapp/js/lib/angular-mocks.js * phoenix-tracing-webapp/src/main/webapp/js/api/chart-model.js * phoenix-tracing-webapp/src/main/webapp/fonts/fontawesome-webfont.svg * phoenix-tracing-webapp/src/main/webapp/js/lib/ui-bootstrap-tpls.js * phoenix-tracing-webapp/src/test/webapp/js/specs/timeline-ctrl-spec.js * phoenix-tracing-webapp/src/main/webapp/fonts/fontawesome-webfont.eot * phoenix-tracing-webapp/src/test/webapp/js/specs/app-route-spec.js * phoenix-tracing-webapp/src/main/webapp/js/controllers/list-controllers.js * phoenix-tracing-webapp/src/main/webapp/js/controllers/trace-distribution-controllers.js * phoenix-tracing-webapp/src/test/webapp/js/specs/trace-list-ctrl-spec.js * phoenix-tracing-webapp/src/main/webapp/js/lib/angular.js * phoenix-tracing-webapp/src/main/webapp/partials/dependency-tree.html * phoenix-tracing-webapp/src/main/webapp/fonts/glyphicons-halflings-regular.eot * phoenix-tracing-webapp/src/main/webapp/js/lib/angular-route.js * phoenix-tracing-webapp/src/main/webapp/js/config/chart-config.js * phoenix-tracing-webapp/src/main/webapp/js/lib/ng-google-chart.js * phoenix-tracing-webapp/src/main/webapp/js/app.js * phoenix-tracing-webapp/src/main/webapp/partials/phoenix-trace.html * phoenix-tracing-webapp/src/main/webapp/js/controllers/dependency-tree-controllers.js * phoenix-tracing-webapp/src/main/webapp/fonts/fontawesome-webfont.ttf * phoenix-tracing-webapp/src/main/webapp/partials/home.html * phoenix-tracing-webapp/src/main/webapp/css/bootstrap.css * phoenix-tracing-webapp/src/main/webapp/js/controllers/accordion-controllers.js * phoenix-tracing-webapp/src/test/webapp/js/specs/tracing-app-ctrl-spec.js * phoenix-tracing-webapp/src/main/webapp/index.html * phoenix-tracing-webapp/src/main/webapp/fonts/FontAwesome.otf * phoenix-tracing-webapp/pom.xml * phoenix-tracing-webapp/src/main/webapp/partials/search.html * phoenix-tracing-webapp/src/main/webapp/css/bootstrap-theme.css.map * phoenix-tracing-webapp/src/main/webapp/partials/contact.html * phoenix-tracing-webapp/src/main/webapp/partials/list.html * phoenix-tracing-webapp/src/main/webapp/js/controllers/timeline-controllers.js * phoenix-tracing-webapp/src/main/webapp/fonts/glyphicons-halflings-regular.woff * phoenix-tracing-webapp/src/main/webapp/fonts/fontawesome-webfont.woff * phoenix-tracing-webapp/src/main/webapp/js/factories/statement-factory-config.js * phoenix-tracing-webapp/src/main/webapp/js/lib/bootstrap.js * phoenix-tracing-webapp/src/main/webapp/fonts/glyphicons-halflings-regular.svg * phoenix-tracing-webapp/src/main/webapp/css/bootstrap-theme.css * phoenix-tracing-webapp/src/main/webapp/css/font-awesome.css * phoenix-tracing-webapp/src/main/webapp/js/services/generate-statement-service.js * phoenix-tracing-webapp/src/main/webapp/partials/help.html * phoenix-tracing-webapp/src/main/webapp/js/controllers/search-controllers.js * phoenix-tracing-webapp/src/main/webapp/js/lib/jquery-2.1.4.js * phoenix-tracing-webapp/src/main/webapp/fonts/fontawesome-webfont.woff2 * phoenix-tracing-webapp/src/main/webapp/partials/chart.html * phoenix-tracing-webapp/src/main/webapp/partials/google-chart.html * phoenix-tracing-webapp/src/main/webapp/css/bootstrap.css.map > Creating the front-end application for Phoenix Tracing Web App > -- > > Key: PHOENIX-2187 > URL: https://issues.apache.org/jira/browse/PHOENIX-2187 > Project: Phoenix > Issue Type: Sub-task >Reporter: Nishani >Assignee: Nishani > Fix For: 4.6.0 > > Attachments: 2187-master.patch > > > This will include the following tracing visualization features. > List - lists the traces with their attributes > Trace Count - Chart view over the trace description > Dependency Tree - tree view of trace ids > Timeline - timeline of trace ids > Trace Distribution - Distribution chart of hosts of traces -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2227) [Pherf] Add ability to execute a DDL statement at the scenario level before any workloads are run
[ https://issues.apache.org/jira/browse/PHOENIX-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Marcel resolved PHOENIX-2227. -- Resolution: Fixed Fix Version/s: 4.5.2 > [Pherf] Add ability to execute a DDL statement at the scenario level before > any workloads are run > - > > Key: PHOENIX-2227 > URL: https://issues.apache.org/jira/browse/PHOENIX-2227 > Project: Phoenix > Issue Type: Improvement >Reporter: Jan Fernando >Assignee: Jan Fernando > Fix For: 4.5.2 > > Attachments: PHOENIX-2227-v2.patch, PHOENIX-2227.patch > > > In order to support Pherf scenarios that write and read from multi-tenant > views it would be useful to add ddl attribute at the scenario level. This DDL > would get run before the workload ran. This would provide a nice hook to > create a mulit-tenant view that we are going to read and write from. This is > analogous to how Pherf allows ddl to be created at the querySet level for > enabling multi-tenant reads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PHOENIX-2184) Pherf - Add plugable custom result writer
[ https://issues.apache.org/jira/browse/PHOENIX-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Marcel resolved PHOENIX-2184. -- Resolution: Fixed Fix Version/s: 4.5.2 > Pherf - Add plugable custom result writer > - > > Key: PHOENIX-2184 > URL: https://issues.apache.org/jira/browse/PHOENIX-2184 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.6.0 >Reporter: Cody Marcel >Assignee: Cody Marcel > Fix For: 4.5.2 > > Attachments: PHOENIX-2184.patch > > > Enhance pherf so that custom implementations of ResultWriter can easily be > added. > This will be property driven so a comma separated list of impl class can be > named in the pherf.properties. > A custom jar can be placed into the /lib folder making it accessible to the > CP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2184) Pherf - Add plugable custom result writer
[ https://issues.apache.org/jira/browse/PHOENIX-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Marcel updated PHOENIX-2184: - Affects Version/s: (was: 4.6.0) 4.5.0 > Pherf - Add plugable custom result writer > - > > Key: PHOENIX-2184 > URL: https://issues.apache.org/jira/browse/PHOENIX-2184 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.5.0 >Reporter: Cody Marcel >Assignee: Cody Marcel > Fix For: 4.5.2 > > Attachments: PHOENIX-2184.patch > > > Enhance pherf so that custom implementations of ResultWriter can easily be > added. > This will be property driven so a comma separated list of impl class can be > named in the pherf.properties. > A custom jar can be placed into the /lib folder making it accessible to the > CP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-1940) Push expected List ordinal position in KeyValueColumnExpression
[
https://issues.apache.org/jira/browse/PHOENIX-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739711#comment-14739711
]
Lars Hofhansl commented on PHOENIX-1940:
Here's another question [~giacomotaylor]: Can I figure out at the time when we
call KeyValueUtil.getColumnLatest whether there is a single column family in
the Phoenix schema? If so, we could even spare the compare of the column
family. This would need to work reliably even for views over existing HBase
tables.
> Push expected List ordinal position in KeyValueColumnExpression
> -
>
> Key: PHOENIX-1940
> URL: https://issues.apache.org/jira/browse/PHOENIX-1940
> Project: Phoenix
> Issue Type: Bug
>Reporter: James Taylor
>
> Looks like quite a bit of time is spent in the binary search done to get the
> latest Cell value when we're evaluating expressions on the server side (up to
> 60% is spent in KeyValueUtil.getColumnLatest()). Since we know the set of
> column qualifiers being projected into the scan, we could push the expected
> position (assuming all columns have values). If the Cell is not in that
> position, we could fall back to a binary search.
> Further enhancements could be to: allow a not null constraint on KeyValue
> columns and either a) require all non null values to be provided on an
> UPSERT, or b) do a check and put to enforce it (for transactional tables this
> could be enforced).
> Additionally, the table could declare that dynamic columns are not allowed.
> If both of the above are true, then we'd be able guaranteed positional access
> the List that we get back from an HBase Scanner.
> One further enhancement would be to collect a set of all ColumnExpression
> instances on the server side for all expressions sent over. Then, we'd bind
> them once, outside of the general expression evaluation of all expressions in
> a statement for a given row. An example of where this would save time would
> be in evaluating the following TPCH-Q1 aggregate query:
> {code}
> SELECT
> l_returnflag,
> l_linestatus,
> sum(l_quantity) as sum_qty,
> sum(l_extendedprice) as sum_base_price,
> sum(l_extendedprice * (1 - l_discount)) as sum_disc_price,
> sum(l_extendedprice * (1 - l_discount) * (1 + l_tax)) as sum_charge,
> avg(l_quantity) as avg_qty,
> avg(l_extendedprice) as avg_price,
> avg(l_discount) as avg_disc,
> count(*) as count_order
> FROM
> lineitem
> WHERE
> l_shipdate <= date '1998-12-01' - interval '90' day
> GROUP BY
> l_returnflag,
> l_linestatus
> ORDER BY
> l_returnflag,
> l_linestatus;
> {code}
> During aggregation, the KeyValueColumnExpression for l_extendedprice would be
> evaluated four times currently, once per occurrence in different SELECT
> expressions. This enhancement would cut that down to once.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (PHOENIX-2248) Simplify uber jars in Phoenix submodules
Mujtaba Chohan created PHOENIX-2248: --- Summary: Simplify uber jars in Phoenix submodules Key: PHOENIX-2248 URL: https://issues.apache.org/jira/browse/PHOENIX-2248 Project: Phoenix Issue Type: Improvement Reporter: Mujtaba Chohan Currently Phoenix-Pherf and Phoenix-Server modules generate uber jars (also Tracing-UI module) that repackages all dependencies. This can be simplified by generating minimal jars for these modules and using Phoenix-client jars on classpath when executing. This is required to reduce the huge size of binary release tar due to duplicate artifacts and also reduces redundancy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-1940) Push expected List ordinal position in KeyValueColumnExpression
[
https://issues.apache.org/jira/browse/PHOENIX-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739759#comment-14739759
]
James Taylor commented on PHOENIX-1940:
---
Yes, we know if we need to compare cf or not (we have different top level
filter classes for this.
> Push expected List ordinal position in KeyValueColumnExpression
> -
>
> Key: PHOENIX-1940
> URL: https://issues.apache.org/jira/browse/PHOENIX-1940
> Project: Phoenix
> Issue Type: Bug
>Reporter: James Taylor
>
> Looks like quite a bit of time is spent in the binary search done to get the
> latest Cell value when we're evaluating expressions on the server side (up to
> 60% is spent in KeyValueUtil.getColumnLatest()). Since we know the set of
> column qualifiers being projected into the scan, we could push the expected
> position (assuming all columns have values). If the Cell is not in that
> position, we could fall back to a binary search.
> Further enhancements could be to: allow a not null constraint on KeyValue
> columns and either a) require all non null values to be provided on an
> UPSERT, or b) do a check and put to enforce it (for transactional tables this
> could be enforced).
> Additionally, the table could declare that dynamic columns are not allowed.
> If both of the above are true, then we'd be able guaranteed positional access
> the List that we get back from an HBase Scanner.
> One further enhancement would be to collect a set of all ColumnExpression
> instances on the server side for all expressions sent over. Then, we'd bind
> them once, outside of the general expression evaluation of all expressions in
> a statement for a given row. An example of where this would save time would
> be in evaluating the following TPCH-Q1 aggregate query:
> {code}
> SELECT
> l_returnflag,
> l_linestatus,
> sum(l_quantity) as sum_qty,
> sum(l_extendedprice) as sum_base_price,
> sum(l_extendedprice * (1 - l_discount)) as sum_disc_price,
> sum(l_extendedprice * (1 - l_discount) * (1 + l_tax)) as sum_charge,
> avg(l_quantity) as avg_qty,
> avg(l_extendedprice) as avg_price,
> avg(l_discount) as avg_disc,
> count(*) as count_order
> FROM
> lineitem
> WHERE
> l_shipdate <= date '1998-12-01' - interval '90' day
> GROUP BY
> l_returnflag,
> l_linestatus
> ORDER BY
> l_returnflag,
> l_linestatus;
> {code}
> During aggregation, the KeyValueColumnExpression for l_extendedprice would be
> evaluated four times currently, once per occurrence in different SELECT
> expressions. This enhancement would cut that down to once.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jira] [Created] (PHOENIX-2244) fix rat violations
Hi,
Ok I will.
On Friday, 11 September 2015, Nick Dimiduk (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/PHOENIX-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739366#comment-14739366
> ]
>
> Nick Dimiduk commented on PHOENIX-2244:
> ---
>
> All the other code is now on master. Please provide a patch based on
> master and I'll make sure it's applied to the active 4.x branches on commit.
>
> > fix rat violations
> > --
> >
> > Key: PHOENIX-2244
> > URL: https://issues.apache.org/jira/browse/PHOENIX-2244
> > Project: Phoenix
> > Issue Type: Sub-task
> >Reporter: Nick Dimiduk
> >Assignee: Nishani
> >Priority: Blocker
> > Fix For: 4.6.0
> >
> >
> > We'll need to resolve the licensing header violations introduced here
> before we can release.
> > {noformat}
> > *
> > Summary
> > ---
> > Generated at: 2015-09-09T16:45:47-07:00
> > Notes: 0
> > Binaries: 9
> > Archives: 1
> > Standards: 53
> > Apache Licensed: 9
> > Generated Documents: 0
> > JavaDocs are generated and so license header is optional
> > Generated files do not required license headers
> > 44 Unknown Licenses
> > ***
> > Unapproved licenses:
> > src/main/webapp/css/bootstrap-theme.css
> > src/main/webapp/css/bootstrap-theme.css.map
> > src/main/webapp/css/bootstrap.css
> > src/main/webapp/css/bootstrap.css.map
> > src/main/webapp/css/font-awesome.css
> > src/main/webapp/fonts/fontawesome-webfont.svg
> > src/main/webapp/fonts/glyphicons-halflings-regular.svg
> > src/main/webapp/index.html
> > src/main/webapp/js/api/chart-model.js
> > src/main/webapp/js/app.js
> > src/main/webapp/js/config/chart-config.js
> > src/main/webapp/js/controllers/accordion-controllers.js
> > src/main/webapp/js/controllers/dependency-tree-controllers.js
> > src/main/webapp/js/controllers/list-controllers.js
> > src/main/webapp/js/controllers/search-controllers.js
> > src/main/webapp/js/controllers/timeline-controllers.js
> > src/main/webapp/js/controllers/trace-count-controllers.js
> > src/main/webapp/js/controllers/trace-distribution-controllers.js
> > src/main/webapp/js/factories/statement-factory-config.js
> > src/main/webapp/js/factories/statement-factory.js
> > src/main/webapp/js/lib/angular-mocks.js
> > src/main/webapp/js/lib/angular-route.js
> > src/main/webapp/js/lib/angular.js
> > src/main/webapp/js/lib/bootstrap.js
> > src/main/webapp/js/lib/jquery-2.1.4.js
> > src/main/webapp/js/lib/jquery.min.js
> > src/main/webapp/js/lib/ng-google-chart.js
> > src/main/webapp/js/lib/ui-bootstrap-tpls.js
> > src/main/webapp/js/services/generate-statement-service.js
> > src/main/webapp/partials/about.html
> > src/main/webapp/partials/chart.html
> > src/main/webapp/partials/contact.html
> > src/main/webapp/partials/dependency-tree.html
> > src/main/webapp/partials/google-chart.html
> > src/main/webapp/partials/help.html
> > src/main/webapp/partials/home.html
> > src/main/webapp/partials/list.html
> > src/main/webapp/partials/phoenix-trace.html
> > src/main/webapp/partials/search.html
> > src/main/webapp/WEB-INF/web.xml
> > src/test/webapp/js/specs/app-route-spec.js
> > src/test/webapp/js/specs/timeline-ctrl-spec.js
> > src/test/webapp/js/specs/trace-list-ctrl-spec.js
> > src/test/webapp/js/specs/tracing-app-ctrl-spec.js
> > {noformat}
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
--
Sent from Gmail Mobile
[jira] [Updated] (PHOENIX-2163) Measure performance of Phoenix/Calcite querying
[ https://issues.apache.org/jira/browse/PHOENIX-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuxiong Ye updated PHOENIX-2163: - Attachment: PhoenixRegressor.log Hi [~maryannxue], I upload the client log, PhoenixRegressor.log, but find no exception in it. Would you mind add testcases and commit it to Branch Calcite, and I will test it in my local environment. I wonder if I have any wrong env setting. > Measure performance of Phoenix/Calcite querying > --- > > Key: PHOENIX-2163 > URL: https://issues.apache.org/jira/browse/PHOENIX-2163 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor >Assignee: Shuxiong Ye > Attachments: PHOENIX-2163.patch, PhoenixRegressor.log, > calcite-test-mac.tar.gz, hbase-logs.7167262.tar.gz, publish.7167262.tar.gz > > > The work to integrate Phoenix with Calcite has come along far enough that > queries both against the data table and through a secondary index is > functional. As a checkpoint, we should compare performance of as many queries > as possible in our regression suite for the calcite branch against the latest > Phoenix release (4.5.0). The runtime of these two systems should be the same, > so this will give us an idea of the overhead of query parsing and compilation > for Calcite. This is super important, as it'll identify outstanding work > that'll be necessary to do prior to any releases on top of this new stack. > Source code of regression suite is at > https://github.com/mujtabachohan/PhoenixRegressor > Connection string location: > https://github.com/mujtabachohan/PhoenixRegressor/blob/master/src/main/resources/settings.json > Instructions on how to compile and run: > https://github.com/mujtabachohan/PhoenixRegressor/blob/master/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Release of Apache Phoenix 4.5.2-HBase-0.98 RC0
Hi Everyone, This is a call for a vote on Apache Phoenix 4.5.2-HBase-0.98 RC0. This is a patch release of Phoenix 4, compatible with the 0.98 branch of Apache HBase. The release includes both a source-only release and a convenience binary release. The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.2-HBase-0.98-rc0/src/ The binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.2-HBase-0.98-rc0/bin/ For a complete list of changes, see: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120&version=1239 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/mujtaba.asc KEYS file available here: https://dist.apache.org/repos/dist/release/phoenix/KEYS The hash and tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=e345a36ee90deeb70fc37e80113eacabce104514 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.5.2-HBase-0.98-rc0 Vote will be open for at least 72 hours. Please vote: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, The Apache Phoenix Team
[VOTE] Release of Apache Phoenix 4.5.2-HBase-1.0 RC0
Hi Everyone, This is a call for a vote on Apache Phoenix 4.5.2-HBase-1.0 RC0. This is a patch release of Phoenix 4, compatible with the 1.0 branch of Apache HBase. The release includes both a source-only release and a convenience binary release. The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.2-HBase-1.0-rc0/src/ The binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.2-HBase-1.0-rc0/bin/ For a complete list of changes, see: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120&version=1239 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/mujtaba.asc KEYS file available here: https://dist.apache.org/repos/dist/release/phoenix/KEYS The hash and tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=4d8b5d28bbe4a01ab6d17a28b6d11a8fe3aa8f6b https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.5.2-HBase-1.0-rc0 Vote will be open for at least 72 hours. Please vote: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, The Apache Phoenix Team
[VOTE] Release of Apache Phoenix 4.5.2-HBase-1.1 RC0
Hi Everyone, This is a call for a vote on Apache Phoenix 4.5.2-HBase-1.1 RC0. This is a patch release of Phoenix 4, compatible with the 1.1 branch of Apache HBase. The release includes both a source-only release and a convenience binary release. The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.2-HBase-1.1-rc0/src/ The binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.5.2-HBase-1.1-rc0/bin/ For a complete list of changes, see: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120&version=1239 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/mujtaba.asc KEYS file available here: https://dist.apache.org/repos/dist/release/phoenix/KEYS The hash and tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=d7c918f272a3503244e72900b545efcd4967c9f1 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.5.2-HBase-1.1-rc0 Vote will be open for at least 72 hours. Please vote: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, The Apache Phoenix Team
[jira] [Commented] (PHOENIX-2239) Honor strict option when catching data error during CSV load
[
https://issues.apache.org/jira/browse/PHOENIX-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740133#comment-14740133
]
James Taylor commented on PHOENIX-2239:
---
Thanks for the patch, [~gabriel.reid]. I suspected that the strict option would
only work for the non MR loader. Perhaps we can file a JIRA to support it for
the MR loader too just to track it?
Couple minor nits:
- Looks like there's some System.out.println() calls left in some of the tests.
- How about passing the original Exception through the errorOnRecord call
instead of just the message? Then wrap it in a RuntimeException. That way, our
JDBC driver will automatically unwrap the RuntimeException and re-throw the
SQLException. It'd be good to keep the csvRecord state in the exception too
somehow - not sure what the best way would be. I supposed we could just log it.
> Honor strict option when catching data error during CSV load
>
>
> Key: PHOENIX-2239
> URL: https://issues.apache.org/jira/browse/PHOENIX-2239
> Project: Phoenix
> Issue Type: Bug
>Reporter: James Taylor
> Attachments: PHOENIX-2239.patch
>
>
> The Phoenix CSV Bulk Loader has a strict option (i.e. -s or --strict) which
> is intended to abort the load if a data error is found. Looks like we're not
> passing this option through the errorOnRecord method, but I think that'd be a
> good (and likely pretty easy) improvement:
> {code}
> @Override
> public void errorOnRecord(CSVRecord csvRecord, String errorMessage) {
> LOG.error("Error upserting record {}: {}", csvRecord,
> errorMessage);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (PHOENIX-2249) SYSTEM.STATS not update after region merge occurs.
Kuan-Po Tseng created PHOENIX-2249: -- Summary: SYSTEM.STATS not update after region merge occurs. Key: PHOENIX-2249 URL: https://issues.apache.org/jira/browse/PHOENIX-2249 Project: Phoenix Issue Type: Bug Environment: Ubuntu server 14.04 Hadoop 2.6.0 HBase 1.0.0 Phoenix 4.4.0-HBase-1.0.0 Reporter: Kuan-Po Tseng When region merge occurs, SYSTEM.STATS does not update, it will leave stale information behind. And then if region splits on the merged region, this may cause "org.apache.phoenix.schema.StaleRegionBoundaryCacheException: ERROR 1108 (XCL08): Cache of region boundaries are out of date" after creating parallel scans since the stale information in SYSTEM.STATS will let guide post list not sorted in ascending order and this will cause scans over regions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PHOENIX-2238) Bulk dataload Hive data with \001 delimiter
[ https://issues.apache.org/jira/browse/PHOENIX-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740246#comment-14740246 ] q79969786 commented on PHOENIX-2238: using -d $'\001' with the error as following: 2015-09-11 13:51:19,490 INFO [main] org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Created MRAppMaster for application appattempt_1441866890289_0446_02 2015-09-11 13:51:19,818 FATAL [main] org.apache.hadoop.conf.Configuration: error parsing conf job.xml org.xml.sax.SAXParseException; systemId: file:///data/M03/yarn/nm/usercache/wym/appcache/application_1441866890289_0446/container_1441866890289_0446_02_01/job.xml; lineNumber: 79; columnNumber: 74; Character reference "&# at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:150) at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2390) at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2459) at org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2412) at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2319) at org.apache.hadoop.conf.Configuration.get(Configuration.java:1146) at org.apache.hadoop.mapreduce.v2.util.MRWebAppUtil.initialize(MRWebAppUtil.java:51) at org.apache.hadoop.mapreduce.v2.app.MRAppMaster.main(MRAppMaster.java:1421) 2015-09-11 13:51:19,821 FATAL [main] org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Error starting MRAppMaster java.lang.RuntimeException: org.xml.sax.SAXParseException; systemId: file:///data/M03/yarn/nm/usercache/wym/appcache/application_1441866890289_0446/container_1441866890289_0446_02_01/job.xml; lineNumber: 79; columnNumber: 74; Character reference "&# at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2555) at org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2412) at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2319) at org.apache.hadoop.conf.Configuration.get(Configuration.java:1146) at org.apache.hadoop.mapreduce.v2.util.MRWebAppUtil.initialize(MRWebAppUtil.java:51) at org.apache.hadoop.mapreduce.v2.app.MRAppMaster.main(MRAppMaster.java:1421) Caused by: org.xml.sax.SAXParseException; systemId: file:///data/M03/yarn/nm/usercache/wym/appcache/application_1441866890289_0446/container_1441866890289_0446_02_01/job.xml; lineNumber: 79; columnNumber: 74; Character reference "&# at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:150) at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2390) at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2459) ... 5 more 2015-09-11 13:51:19,823 INFO [main] org.apache.hadoop.util.ExitUtil: Exiting with status 1 > Bulk dataload Hive data with \001 delimiter > --- > > Key: PHOENIX-2238 > URL: https://issues.apache.org/jira/browse/PHOENIX-2238 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.3.0 >Reporter: q79969786 > > Bulk dataload : > hadoop jar > /opt/cloudera/parcels/CLABS_PHOENIX-4.3.0-1.clabs_phoenix1.0.0.p0.78/lib/phoenix/phoenix-4.3.0-clabs-phoenix-1.0.0-client.jar > org.apache.phoenix.mapreduce.CsvBulkLoadTool --table test_phoenix_import > --zookeeper n1,n2,n3 --delimiter \001 --input /user/wym/test_phoenix_import > The path ‘/user/wym/test_phoenix_import’ is a directory contains Hive data, > so the default delimiter is \001. > Exception: > 15/09/08 15:22:17 INFO zookeeper.ClientCnxn: EventThread shut down > 15/09/08 15:22:17 INFO zookeeper.ZooKeeper: Session: 0x34f1c9be8ba5667 closed > Exception in thread "main" java.lang.IllegalArgumentException: Illegal > delimiter character: 001 > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.configureOptions(CsvBulkLoadTool.java:327) > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.loadData(CsvBulkLoadTool.java:201) > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.run(CsvBulkLoadTool.java:186) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at > org.apache.phoenix.mapreduce.CsvBulkLoadTool.main(CsvBulkLoadTool.java:97) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAcc
