Issue Type: Bug
> > Affects Versions: 4.0.0, 4.1
> >Reporter: James Taylor
> >Assignee: Jesse Yates
> > Attachments: phoenix-938-4.0-v0.patch,
> phoenix-938-master-v0.patch, phoenix-938-master-v1.patch
> >
> >
> >
[
https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007791#comment-14007791
]
Jesse Yates commented on PHOENIX-938:
-
The other caveat is we need to update
[
https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-938:
Attachment: phoenix-938-master-v1.patch
phoenix-938-4.0-v0.patch
Attaching
Well done all! Congrats!
On May 22, 2014 10:24 AM, "Mujtaba Chohan" wrote:
> Great news!!! :) Congrats all...
>
>
> On Thu, May 22, 2014 at 10:21 AM, Eli Levine wrote:
>
> > Truly awesome. It has been great to witness the project's transition
> from
> > an internal proof of concept all the way
[
https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983391#comment-13983391
]
Jesse Yates commented on PHOENIX-938:
-
I actually wrote the code up last week,
ache Phoenix Project:
>
> * Andrew Purtell
> * Anoop Sam John
> * Devaraj Das
> * Eli Levine
> * Enis Soztutar
> * Gabriel Reid
> * James R. Taylor
> * Jeffrey
[
https://issues.apache.org/jira/browse/PHOENIX-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980018#comment-13980018
]
Jesse Yates commented on PHOENIX-950:
-
Not having read the doc yet, I'd re
[
https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977099#comment-13977099
]
Jesse Yates commented on PHOENIX-938:
-
Oh, I like that much better! I knew if I
[
https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-938:
Attachment: phoenix-938-master-v0.patch
Initial patch to support custom queue usage on both the
[
https://issues.apache.org/jira/browse/PHOENIX-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974389#comment-13974389
]
Jesse Yates commented on PHOENIX-848:
-
I'm not sure what you mean by &q
onfig option maybe?).
---
Jesse Yates
@jesse_yates
jyates.github.com
On Thu, Apr 17, 2014 at 11:27 AM, Andrew Purtell wrote:
> On Thu, Apr 17, 2014 at 10:26 AM, James Taylor >wrote:
>
> > If possible, it'd be good to target this one too:
> > - prevent de
+1
Works really well for HBase since there is a lot of change over there. I
don't know if we are at that volume, but even around 10ish changes per
release is reasonable. Overall, I'm generally +1 on the release train as
long as the RM is up for it, of course :)
-------
J
Congrats and welcome Gabriel!
---
Jesse Yates
@jesse_yates
jyates.github.com
On Tue, Apr 8, 2014 at 10:23 AM, James Taylor wrote:
> On behalf of the Apache Phoenix project, I am pleased to welcome Gabriel
> Reid as a committer. He stepped in and did a fantastic job re-w
[
https://issues.apache.org/jira/browse/PHOENIX-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-871:
Attachment: phoenix-871-master.txt
phoenix-871-3.0.txt
Attaching patches for 3.0
[
https://issues.apache.org/jira/browse/PHOENIX-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates resolved PHOENIX-871.
-
Resolution: Fixed
Committed to 3.0, 4.0 and master branches.
> Mutable Secondary Indexing
[
https://issues.apache.org/jira/browse/PHOENIX-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939647#comment-13939647
]
Jesse Yates commented on PHOENIX-871:
-
Pull request here: https://github.com/ap
Jesse Yates created PHOENIX-871:
---
Summary: Mutable Secondary Indexing can cause a deadlock on
exception
Key: PHOENIX-871
URL: https://issues.apache.org/jira/browse/PHOENIX-871
Project: Phoenix
full semantic versioning; even if so, we could
keep the current number to help cut down on the number of branches we would
need to commit to. Then we could have a vote for cutting a new branch (5.0,
and bumping master to 5.1) when we need to have a breaking/incompatible
change.
---
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates resolved PHOENIX-842.
-
Resolution: Fixed
> Use better namespace for maven artifa
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934328#comment-13934328
]
Jesse Yates commented on PHOENIX-842:
-
Committed to 3.0, 4.0 and master bran
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-842:
Fix Version/s: 4.0.0
3.0.0
> Use better namespace for maven artifa
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933917#comment-13933917
]
Jesse Yates commented on PHOENIX-842:
-
Sounds good to me! I'll commit this
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933899#comment-13933899
]
Jesse Yates edited comment on PHOENIX-842 at 3/13/14 7:0
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933899#comment-13933899
]
Jesse Yates commented on PHOENIX-842:
-
+1 on latest patch. Tested locally and w
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932714#comment-13932714
]
Jesse Yates commented on PHOENIX-842:
-
Nope, the patch isn't going work th
[
https://issues.apache.org/jira/browse/PHOENIX-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932675#comment-13932675
]
Jesse Yates commented on PHOENIX-842:
-
+1
> Use better namespace fo
+1
---
Jesse Yates
@jesse_yates
jyates.github.com
On Thu, Mar 6, 2014 at 3:43 PM, James Taylor wrote:
> Hey All,
> I'd like to branch master to 3.0 so that 4.0 can become the master branch.
> There are a couple of outstanding changes that I'd like to compl
I'd rather do that one layer up as I proposed in the PhoenixWriterCommiter
- it helps separate concerns for cases where users want to use the indexing
but don't want all the rest of the phoenix stuff.
-------
Jesse Yates
@jesse_yates
jyates.github.com
On Wed, Mar 5, 2014
[
https://issues.apache.org/jira/browse/PHOENIX-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921874#comment-13921874
]
Jesse Yates commented on PHOENIX-113:
-
Agree that for the 4.X line Cell is the
[
https://issues.apache.org/jira/browse/PHOENIX-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921873#comment-13921873
]
Jesse Yates commented on PHOENIX-113:
-
The problem is going from Cell -> K
[
https://issues.apache.org/jira/browse/PHOENIX-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-113:
Attachment: phoenix-113-sketch.txt
Attaching a sketch of how one might go about implementing an
[
https://issues.apache.org/jira/browse/PHOENIX-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-113:
Summary: Enable usage of ClientKeyValue on for indexing on server (was:
Enable usage of
g the
-client-without-hbase jar would be a good idea, so you don't clobber the
classpath with your own HBase dependencies.
Take a look at the pom and assembly descriptors in phoenix-assembly to see
how these things all work.
-------
Jesse Yates
@jesse_yates
jyates.github.com
On
[
https://issues.apache.org/jira/browse/PHOENIX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates resolved PHOENIX-78.
Resolution: Fixed
> MetaDataUtil must respect ClientKeyValue us
[
https://issues.apache.org/jira/browse/PHOENIX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915334#comment-13915334
]
Jesse Yates commented on PHOENIX-78:
It doesn't look too terrible
[
https://issues.apache.org/jira/browse/PHOENIX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-78:
---
Attachment: phoenix-78-v2.patch
Here we go again. Probably not as big a deal now that ClientKeyValue
[
https://issues.apache.org/jira/browse/PHOENIX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913956#comment-13913956
]
Jesse Yates commented on PHOENIX-78:
I was thinking of that when I wrote it.
[
https://issues.apache.org/jira/browse/PHOENIX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-78:
---
Attachment: phoenix-78-v1.patch
Thanks for the review James! Attaching patch with updates.
Besides
[
https://issues.apache.org/jira/browse/PHOENIX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-78:
---
Attachment: phoenix-78-v0.patch
Attaching patch.
Now KeyValueBuilder becomes the interface behind
[
https://issues.apache.org/jira/browse/PHOENIX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913788#comment-13913788
]
Jesse Yates commented on PHOENIX-78:
[~giacomotaylor] I think this is what we ta
Jesse Yates created PHOENIX-78:
--
Summary: MetaDataUtil must respect ClientKeyValue usage
Key: PHOENIX-78
URL: https://issues.apache.org/jira/browse/PHOENIX-78
Project: Phoenix
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PHOENIX-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911891#comment-13911891
]
Jesse Yates commented on PHOENIX-53:
+1 on pom - lgtm. I think we should be
[
https://issues.apache.org/jira/browse/PHOENIX-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates resolved PHOENIX-58.
Resolution: Fixed
Closing. Thanks for the review James.
> Client jars are missing phoenix c
[
https://issues.apache.org/jira/browse/PHOENIX-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907645#comment-13907645
]
Jesse Yates commented on PHOENIX-53:
{quote}
4. Could someone assist with remo
[
https://issues.apache.org/jira/browse/PHOENIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates resolved PHOENIX-57.
Resolution: Fixed
Commited to master. Thanks for the review James!
> ClientKeyValue doesn
[
https://issues.apache.org/jira/browse/PHOENIX-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-58:
---
Attachment: phoenix-58-v0.patch
client-without-hbase-jar.txt
client
Jesse Yates created PHOENIX-58:
--
Summary: Client jars are missing phoenix code
Key: PHOENIX-58
URL: https://issues.apache.org/jira/browse/PHOENIX-58
Project: Phoenix
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/PHOENIX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904491#comment-13904491
]
Jesse Yates commented on PHOENIX-38:
awesome, thanks Mujtaba!
> Data load ti
[
https://issues.apache.org/jira/browse/PHOENIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904479#comment-13904479
]
Jesse Yates commented on PHOENIX-57:
[~giacomotaylor] mind taking a look? i
[
https://issues.apache.org/jira/browse/PHOENIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-57:
---
Attachment: phoenix-57-v0.patch
> ClientKeyValue doesn't work in de
[
https://issues.apache.org/jira/browse/PHOENIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates reassigned PHOENIX-57:
--
Assignee: Jesse Yates
> ClientKeyValue doesn't work in de
Jesse Yates created PHOENIX-57:
--
Summary: ClientKeyValue doesn't work in debug mode
Key: PHOENIX-57
URL: https://issues.apache.org/jira/browse/PHOENIX-57
Project: Phoenix
Issue Type
[
https://issues.apache.org/jira/browse/PHOENIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904476#comment-13904476
]
Jesse Yates commented on PHOENIX-57:
Since this only occurs in debugging, we d
[
https://issues.apache.org/jira/browse/PHOENIX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898072#comment-13898072
]
Jesse Yates commented on PHOENIX-38:
Sounds like someone else changed some s
, this allows you to easily track that state).
--j
---
Jesse Yates
@jesse_yates
jyates.github.com
On Mon, Feb 10, 2014 at 4:03 PM, lars hofhansl wrote:
> Personally I'd be in favor of 4.0.0 as this conveys the fact that we do
> semantic versioning.
> As usually
+1
Caveat that that 4.1, 4.2 lines should probably get their own branches.
---
Jesse Yates
@jesse_yates
jyates.github.com
On Mon, Feb 10, 2014 at 3:50 PM, James Taylor wrote:
> Sure, 4.0 is fine. I think we can just tag our minor and point releases
> instead of cr
+1
On Feb 6, 2014 6:46 PM, "Eli Levine" wrote:
> +1
>
>
> On Thu, Feb 6, 2014 at 3:30 PM, Andrew Purtell
> wrote:
>
> > +1
> >
> >
> > On Thu, Feb 6, 2014 at 11:02 AM, Stack wrote:
> >
> > > We, Apache Phoenix (incubating), need to vote on whether we accept the
> > > donation by Salesforce of t
OK, this is a bit hacky, but could work. Basically, take a look at the
phoenix assembly files and specifically how the client jar is built - if
just a whitelist (iirc) of dependencies. Similarly you could build one that
doesn't include the offending dependencies that provide the Servlet class.
You
On Thu, Jan 30, 2014 at 5:03 PM, James Taylor wrote:
> In what format is the patch given to you? Is it (or can it be) a git-diff?
>
HBase supports both svn and git. We can just support git for phoenix
> And how do you visually apply the patch so that you can see it in the
> context of the code
AFAIK, no one is working on this, but it sounds pretty cool!
Mind filling a JIRA?
Thanks,
J
On Jan 30, 2014 7:28 AM, "rajeshbabu chintaguntla" <
rajeshbabu.chintagun...@huawei.com> wrote:
> Hi,
>
> Normally when we want to use secondary indices we create index on one or
> very few
> columns of i
much time verifying each
patch (running all the tests, etc).
-------
Jesse Yates
@jesse_yates
jyates.github.com
On Wed, Jan 29, 2014 at 8:42 AM, James Taylor wrote:
> Gerrit sounds interesting. Sounds like infra dismissed it though. Will ask
> about this on the general li
Git is just a source control system - it was github that lead to the
prevalence of the pull requests and merges.
Whatever we do for reviews, we basically need to use git like svn and fully
sync the repo each time, apply the patch, and then commit. Git hosting just
means ppl work in the same source
Sweet! Awesome to see it finally move.
Thanks James!
On Jan 27, 2014 2:58 PM, "James Taylor" wrote:
> I've seeded our master branch based on our master from github. Our official
> git repo is located here:
> https://git-wip-us.apache.org/repos/asf/incubator-phoenix.git in case you
> don't know.
[
https://issues.apache.org/jira/browse/PHOENIX-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876669#comment-13876669
]
Jesse Yates commented on PHOENIX-5:
---
If you know you are on the same server, can
PMC members elected?
> >> >
> >> > No new committers or PMC members.
> >> >
> >> >
> >> > 1.
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2
> >> > 2. http://phoenix.incubator.apache.org/
> >> >
> >>
>
> --
> 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.
>
--
---
Jesse Yates
@jesse_yates
jyates.github.com
65 matches
Mail list logo
