It's your party James, in my opinion.
On Friday, January 31, 2014, James Taylor wrote:
> The folks over at jcloud use this as their methodology:
> http://wiki.apache.org/jclouds/Committers%20Guide
>
> Seems reasonable to me (with my Github bias :-)
>
> Thoughts?
>
>
> On Thu, Jan 30, 2014 at 6:5
Also, I would be interested to know if phoenix gathers any stats now?
Thanks
Abhishek
On 01/31/2014 10:46 PM, abhishek wrote:
Hi James
I am building a schema recommendation system based on cost modeling.
Currently, I gather all necessary features off line using phoenix
queries or hbase api. H
Hi James
I am building a schema recommendation system based on cost modeling.
Currently, I gather all necessary features off line using phoenix
queries or hbase api. However, as you mentioned in your mail, these
stats can be gathered efficiently during major compaction or by using
other backg
Hi,
This is a good start. How do you get the number of rows per table?
I think the biggest missing piece is histogram information so you can
approximate cardinalities. We thought to track this through a stats
collection process done during major compaction. And, of course, the query
engine needs t
The folks over at jcloud use this as their methodology:
http://wiki.apache.org/jclouds/Committers%20Guide
Seems reasonable to me (with my Github bias :-)
Thoughts?
On Thu, Jan 30, 2014 at 6:50 PM, James Taylor wrote:
> Seems like Jake said "no" by closing it the INFRA ticket. I'll ask on the
>
[
https://issues.apache.org/jira/browse/PHOENIX-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888386#comment-13888386
]
abhishek edited comment on PHOENIX-16 at 2/1/14 2:06 AM:
-
Thanks M
[
https://issues.apache.org/jira/browse/PHOENIX-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888386#comment-13888386
]
abhishek commented on PHOENIX-16:
-
Thanks Maryann. It worked.
I am currently working on c
[
https://issues.apache.org/jira/browse/PHOENIX-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888384#comment-13888384
]
Maryann Xue edited comment on PHOENIX-16 at 2/1/14 1:43 AM:
Ac
[
https://issues.apache.org/jira/browse/PHOENIX-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888384#comment-13888384
]
Maryann Xue commented on PHOENIX-16:
Actually o.o_orderkey < 100 should be put in on c
[
https://issues.apache.org/jira/browse/PHOENIX-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888348#comment-13888348
]
abhishek commented on PHOENIX-16:
-
*o.o_orderkey<100;
> Join Query optimization
> ---
[
https://issues.apache.org/jira/browse/PHOENIX-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888347#comment-13888347
]
abhishek commented on PHOENIX-16:
-
Both workaround queries throw this error: Error: Does n
bq. Any optimizer folks out there interested in getting involved?
Some oracle expert team is available here James. Hope they will help if
needed.
Thanks,
Rajeshbabu.
On Thu, Jan 30, 2014 at 10:00 PM, James Taylor wrote:
> It's on our roadmap, but we need to collect stats first to drive optimize
Anil Gupta created PHOENIX-19:
-
Summary: Enhance JDBC connection of Phoenix to support connecting
to a Secure HBase cluster.
Key: PHOENIX-19
URL: https://issues.apache.org/jira/browse/PHOENIX-19
Project:
saravanan created PHOENIX-18:
Summary: problem in sort for (count(distinct col)) DESC
Key: PHOENIX-18
URL: https://issues.apache.org/jira/browse/PHOENIX-18
Project: Phoenix
Issue Type: Bug
14 matches
Mail list logo
