your work to master at that point. Doubtless
>> > you
>> > >>>> would need new features & bug fixes in Calcite after that, and so
>> work
>> > >>> that
>> > >>>> depended on that would have to stay in a branch
; depended on that would have to stay in a branch until Calcite was
> > >>> released.
> > >>>>
> > >>>> Julian
> > >>>>
> > >>>> On Feb 11, 2015, at 10:34 AM, Felix GV
> > >
> > >>>
y
> >>>> they'll be included in the next release, which may not be the case if
> >>>> they're still considered very experimental.
> >>>>>
> >>>>> Alternatively, perhaps Julian can create a new version name with a
> >
y
>>>> they'll be included in the next release, which may not be the case if
>>>> they're still considered very experimental.
>>>>>
>>>>> Alternatively, perhaps Julian can create a new version name with a
>>>> classifier for streaming.
>&
rhaps Julian can create a new version name with a
> >> > classifier for streaming.
> >> > >
> >> > >
> >> >
> >>
> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
> >> > &g
> > >
>> >
>> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
>> > >
>> > > Then he could release SNAPSHOT artifacts for both the main/master code
>> > base as well as the streaming branch
sifiers.html
> > >
> > > Then he could release SNAPSHOT artifacts for both the main/master code
> > base as well as the streaming branch, no matter how experimental it is...
> > >
> > > --
> > >
> > > Felix GV
> > > Data Infrastructure Engineer
>
streaming branch, no matter how experimental it is...
> >
> > --
> >
> > Felix GV
> > Data Infrastructure Engineer
> > Distributed Data Systems
> > LinkedIn
> >
> > f...@linkedin.com
> > linkedin.com/in/felixgv
> >
> > ___
__
> From: Chris Riccomini [criccom...@apache.org]
> Sent: Wednesday, February 11, 2015 10:23 AM
> To: Chris Riccomini
> Cc: dev@samza.apache.org
> Subject: Re: [DISCUSS] SQL workflow
>
> Hey Julian,
>
> It looks like Calcite is at least setup to publ
s
LinkedIn
f...@linkedin.com
linkedin.com/in/felixgv
From: Chris Riccomini [criccom...@apache.org]
Sent: Wednesday, February 11, 2015 10:23 AM
To: Chris Riccomini
Cc: dev@samza.apache.org
Subject: Re: [DISCUSS] SQL workflow
Hey Julian,
It looks like Cal
Hey Julian,
It looks like Calcite is at least setup to publish to Maven:
https://repository.apache.org/#nexus-search;quick~calcite
Julian, can you publish SNAPSHOT releases with your streaming changes to it?
Thanks!
Chris
On Wed, Feb 11, 2015 at 10:08 AM, Chris Riccomini
wrote:
> Hey Milin
Hey Milinda,
I've just committed SAMZA-484, so you should be able to re-base and get all
the latest code.
> But we need to add Calcite as a dependency and Calcite streaming support
is only in Julian's branch
We'll have to have Julian publish a release to Apache. This can be a
SNAPSHOT to Apache'
No, SAMZA-483 doesn't depend on SAMZA-484. But we need to add Calcite as a
dependency and Calcite streaming support is only in Julian's branch (
https://github.com/julianhyde/incubator-calcite/tree/chi). What can we do
about that?
Milinda
On Wed, Feb 11, 2015 at 12:30 PM, Chris Riccomini
wrote:
Hey Milinda,
That'd be great. Do you have any dependency on SAMZA-484? I haven't had a
chance to commit that one yet.
Cheers,
Chris
On Wed, Feb 11, 2015 at 9:23 AM, Milinda Pathirage
wrote:
> /need/want
>
> Milinda
>
> On Wed, Feb 11, 2015 at 12:22 PM, Milinda Pathirage >
> wrote:
>
> > Hi Ch
/need/want
Milinda
On Wed, Feb 11, 2015 at 12:22 PM, Milinda Pathirage
wrote:
> Hi Chris,
>
> Do you need me to create the SAMZA-483 patch against latest master with
> SAMZA-482 patch? I think that will make it easier to review the patch?
>
> Thanks
> Milinda
>
> On Mon, Feb 9, 2015 at 11:39 AM
Hi Chris,
Do you need me to create the SAMZA-483 patch against latest master with
SAMZA-482 patch? I think that will make it easier to review the patch?
Thanks
Milinda
On Mon, Feb 9, 2015 at 11:39 AM, Chris Riccomini
wrote:
> Cool. Looks like we've got consensus. I'll move forward with RTC on
Cool. Looks like we've got consensus. I'll move forward with RTC on some of
the early SAMZA-390 tickets. (SAMZA-482, SAMZA-483, SAMZA-484)
On Mon, Feb 9, 2015 at 8:35 AM, Yan Fang wrote:
> +1 on this.
>
> Fang, Yan
> yanfang...@gmail.com
> +1 (206) 849-4108
>
> On Fri, Feb 6, 2015 at 4:38 PM, Ch
+1 on this.
Fang, Yan
yanfang...@gmail.com
+1 (206) 849-4108
On Fri, Feb 6, 2015 at 4:38 PM, Chris Riccomini
wrote:
> Hey all,
>
> Are we +1 on this? I think Jakob was the only one who was curious about it.
>
> Cheers,
> Chris
>
> On Thu, Feb 5, 2015 at 1:22 PM, Yi Pan wrote:
>
> > Hi, Jakob,
+1
On Sat, Feb 7, 2015 at 8:38 AM, Chris Riccomini
wrote:
> Hey all,
>
> Are we +1 on this? I think Jakob was the only one who was curious about it.
>
> Cheers,
> Chris
>
> On Thu, Feb 5, 2015 at 1:22 PM, Yi Pan wrote:
>
> > Hi, Jakob,
> >
> >
> > > > Eh? Not sure what this means...
> > >
> > >
+1.
On 6 February 2015 at 16:38, Chris Riccomini wrote:
> Hey all,
>
> Are we +1 on this? I think Jakob was the only one who was curious about it.
>
> Cheers,
> Chris
>
> On Thu, Feb 5, 2015 at 1:22 PM, Yi Pan wrote:
>
>> Hi, Jakob,
>>
>>
>> > > Eh? Not sure what this means...
>> >
>> > I mean S
Hey all,
Are we +1 on this? I think Jakob was the only one who was curious about it.
Cheers,
Chris
On Thu, Feb 5, 2015 at 1:22 PM, Yi Pan wrote:
> Hi, Jakob,
>
>
> > > Eh? Not sure what this means...
> >
> > I mean SAMZA-484 depends on SAMZA-482, and neither are committed. So
> Navina
> > is h
Hi, Jakob,
> > Eh? Not sure what this means...
>
> I mean SAMZA-484 depends on SAMZA-482, and neither are committed. So Navina
> is having to post Yi's patch, as well as her own, on the JIRA. It makes it
> really hard to do code reviews because you can't tell whether Yi made the
> changes or Navi
Hey Jakob,
> Just curious, any reason for this?
Every time I've seen major feature work done on a branch, the branch
diverges from master to the point where no one feels comfortable merging
it, or it gets abandoned, or something. Example A would be the
transactional Kafka branch. Example B would
> I want to avoid branches,
Just curious, any reason for this?
> and I also want to avoid revision control over JIRA
Eh? Not sure what this means...
Thanks,
jg
On 4 February 2015 at 17:11, Chris Riccomini wrote:
> Hey all,
>
> @Jakob, yeah I was thinking we'll follow our normal flow. RTC. I ju
Hey all,
@Jakob, yeah I was thinking we'll follow our normal flow. RTC. I just
wanted to set expectation that the code committed might be not up to our
normal quality initially (missing docs, no tests, etc). Until the quality
is raised, we should think of this module as experimental.
@Milinda, aw
Hi Chris,
Hope we no longer need the SQL API. I'll create a RB for Calcite
integration.
Thanks
Milinda
On Wed, Feb 4, 2015 at 1:31 PM, Chris Riccomini
wrote:
> I think so. There was some RB downtime, but it just got fixed. Yi, Navina,
> Milinda, can you make sure your JIRAs have up to date RBs
Hi, Jacob,
Yes, for sure.
-Yi
On Wed, Feb 4, 2015 at 11:43 AM, Jakob Homan wrote:
> This submodule will still be under the review-then-commit (RTC)
> regime, correct?
>
> On 4 February 2015 at 11:13, Yi Pan wrote:
> > Just did the update w/ SAMZA-482.
> >
> > On Wed, Feb 4, 2015 at 10:31 AM,
This submodule will still be under the review-then-commit (RTC)
regime, correct?
On 4 February 2015 at 11:13, Yi Pan wrote:
> Just did the update w/ SAMZA-482.
>
> On Wed, Feb 4, 2015 at 10:31 AM, Chris Riccomini
> wrote:
>
>> I think so. There was some RB downtime, but it just got fixed. Yi, Na
I have updates SAMZA-484 and RB is here -
https://reviews.apache.org/r/30634/diff/#
Navina
On 2/4/15, 11:13 AM, "Yi Pan" wrote:
>Just did the update w/ SAMZA-482.
>
>On Wed, Feb 4, 2015 at 10:31 AM, Chris Riccomini
>wrote:
>
>> I think so. There was some RB downtime, but it just got fixed. Yi,
Just did the update w/ SAMZA-482.
On Wed, Feb 4, 2015 at 10:31 AM, Chris Riccomini
wrote:
> I think so. There was some RB downtime, but it just got fixed. Yi, Navina,
> Milinda, can you make sure your JIRAs have up to date RBs?
>
> On Wed, Feb 4, 2015 at 10:24 AM, sriram wrote:
>
> > Can we hav
I think so. There was some RB downtime, but it just got fixed. Yi, Navina,
Milinda, can you make sure your JIRAs have up to date RBs?
On Wed, Feb 4, 2015 at 10:24 AM, sriram wrote:
> Can we have updated RBs for all the three sub tasks before we commit? This
> would help us to review even after w
Can we have updated RBs for all the three sub tasks before we commit? This
would help us to review even after we commit.
On Wed, Feb 4, 2015 at 10:15 AM, Chris Riccomini
wrote:
> Hey all,
>
> Yi, Navina, and Milinda have been working on SAMZA-390 sub-tickets related
> to SQL operators. We're get
Hey all,
Yi, Navina, and Milinda have been working on SAMZA-390 sub-tickets related
to SQL operators. We're getting to the point where the amount of work
floating around is quite large, and some tickets build off of others.
I'm proposing that we commit this work into a samza-sql submodule on
mast
33 matches
Mail list logo
