Re: Branch deletion prohibited

[Raul Kripalani]

Exactly. Let's wait for Infra's feedback on why that restriction and when
it'll be lifted.

[jira] [Created] (IGNITE-1950) Binary format: Arrays and collections use handles differently in Java and platforms.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1950:
---

 Summary: Binary format: Arrays and collections use handles 
differently in Java and platforms.
 Key: IGNITE-1950
 URL: https://issues.apache.org/jira/browse/IGNITE-1950
 Project: Ignite
  Issue Type: Bug
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


In Java arrays and collections could use handles. In .Net and CPP they can't. 
We need to provide unified approach for all platforms.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Ignite-1.5 Release

[Romain Gilles]

Hi Raul,
Could you please give the pull request or the branch or the ignite ticket
number?
I will be please to have a look to your pull request.

Thanks,

Romain

Le jeu. 19 nov. 2015 à 04:01, Dmitriy Setrakyan  a
écrit :

> On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani  wrote:
>
> > I merged the Camel Streamer today and I hope to finish the first phase of
> > OSGi tomorrow.
> >
> > I'll need someone to review the latter quickly if we want it merged for
> > 1.5... No code changes in existing codebase. Just a new osgi module and
> > many POM changes mainly to generate the manifests.
> >
>
> Raul, did you create a patch or a PR? I can’t find it anywhere.
>
>
> >
> > Should be a quick task.
> >
> > Regards,
> > Raúl.
> > On 18 Nov 2015 20:38, "Vladimir Ozerov"  wrote:
> >
> > > Hi Alex,
> > >
> > > Today I marged several big things into 1282 - reworked metadat and
> > > compacted footers optimization. I have on big ticket left -
> IGNITE-1917 -
> > > with marshalling microoptimizations. They should not conflict with
> > anything
> > > and I expect them to be finalized tomorrow. All optimizations are
> ready,
> > I
> > > just need to perform some cleanup and refactoring.
> > >
> > > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > > alexey.goncha...@gmail.com> wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I merged performance optimizations for tx mode which gave up to 5%
> > > > improvement for tx-put benchmark to ignite-1.5.
> > > >
> > > > I also pushed finalizaing changes to Binary configuration in
> > ignite-1945
> > > > branch and currently waiting for TC. If all is ok, will cooperate
> with
> > > > Vladimir Ozerov and merge changes tomorrow.
> > > >
> > > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov :
> > > >
> > > > > Hi,
> > > > >
> > > > > Yesterday I merged optimizations for tx update operations working
> > > single
> > > > > key, got ~7% improvement in tx-put benchmark.
> > > > >
> > > > > And today I finished to implement optimization for cache 'get'
> > > operation
> > > > > with single key. Got another benchmark results improvements: ~10%
> > with
> > > > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and
> hopefully
> > > will
> > > > > merge these changes tomorrow.
> > > > >
> > > > > ​
> > > > >
> > > >
> > >
> >
>

Javadoc warnings at Ignite 1.5

[Anton Vinogradov]

Hello,

I've checked output of prerelease build of Ignite 1.5 and found javadoc
warnings like
CamelStreamer.java:51: warning - Tag @link: malformed:
"StreamMultipleTupleExtractor)"

Raul, seems that was your changes. Could you please fix it?

Re: Branch deletion prohibited

[Artem Shutak]

Dmitriy,

No, according to a note [1] on the wiki page [2] we need to check on
unmerged changes before. Looks like we should add a status column (someone
already has proposed it) where we can track is a branch ready to delete or
not.

[1] *Note. We don’t remove any *unmerged* branches. Even if the ticket was
closed, it is possible that we forgot to merge. Before deleting a branch,
we take an extra step to verify that the changes are in the master.*
[2]
https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete

-- Artem --

On Thu, Nov 19, 2015 at 12:04 PM, Dmitriy Setrakyan 
wrote:

> Should we file a ticket with INFRA asking them to delete all the branches
> listed on this page:
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
>
> Is it safe?
>
> D.
>
> On Thu, Nov 19, 2015 at 12:57 AM, Yakov Zhdanov 
> wrote:
>
> > Guys, therefore, let's develop new functionality in personal forks, test
> on
> > TC with pull requests and then merge to apache git as described here -
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >
> > We should create new branches only if this is really necessary.
> >
> > Thanks!
> > --
> > Yakov Zhdanov, Director R
> > *GridGain Systems*
> > www.gridgain.com
> >
> > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan :
> >
> > > Raul,
> > >
> > > ASF is currently prohibiting deletion of GIT branches until further
> > notice.
> > > Please add your branch to this Wiki page, so we don’t loose track:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > >
> > > Thanks,
> > > D.
> > >
> > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani 
> > wrote:
> > >
> > > > Fellows,
> > > >
> > > > I'm trying to push a branch deletion and the ASF Git tells me that
> > branch
> > > > deletion is prohibited.
> > > >
> > > > Has someone changed something?
> > > >
> > > > [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790
> > > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > error: failed to push some refs to '
> > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > >
> > > > Regards,
> > > >
> > > > *Raúl Kripalani*
> > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> > and
> > > > Messaging Engineer
> > > > http://about.me/raulkripalani |
> > http://www.linkedin.com/in/raulkripalani
> > > > http://blog.raulkr.net | twitter: @raulvk
> > > >
> > >
> >
>

Re: Ignite-1.5 Release

[Raul Kripalani]

Branch ignite-1790 merged into ignite-1.5 with --squash. Like it was
requested previous on previous occasions.
On 19 Nov 2015 03:01, "Dmitriy Setrakyan"  wrote:

> On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani  wrote:
>
> > I merged the Camel Streamer today and I hope to finish the first phase of
> > OSGi tomorrow.
> >
> > I'll need someone to review the latter quickly if we want it merged for
> > 1.5... No code changes in existing codebase. Just a new osgi module and
> > many POM changes mainly to generate the manifests.
> >
>
> Raul, did you create a patch or a PR? I can’t find it anywhere.
>
>
> >
> > Should be a quick task.
> >
> > Regards,
> > Raúl.
> > On 18 Nov 2015 20:38, "Vladimir Ozerov"  wrote:
> >
> > > Hi Alex,
> > >
> > > Today I marged several big things into 1282 - reworked metadat and
> > > compacted footers optimization. I have on big ticket left -
> IGNITE-1917 -
> > > with marshalling microoptimizations. They should not conflict with
> > anything
> > > and I expect them to be finalized tomorrow. All optimizations are
> ready,
> > I
> > > just need to perform some cleanup and refactoring.
> > >
> > > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > > alexey.goncha...@gmail.com> wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I merged performance optimizations for tx mode which gave up to 5%
> > > > improvement for tx-put benchmark to ignite-1.5.
> > > >
> > > > I also pushed finalizaing changes to Binary configuration in
> > ignite-1945
> > > > branch and currently waiting for TC. If all is ok, will cooperate
> with
> > > > Vladimir Ozerov and merge changes tomorrow.
> > > >
> > > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov :
> > > >
> > > > > Hi,
> > > > >
> > > > > Yesterday I merged optimizations for tx update operations working
> > > single
> > > > > key, got ~7% improvement in tx-put benchmark.
> > > > >
> > > > > And today I finished to implement optimization for cache 'get'
> > > operation
> > > > > with single key. Got another benchmark results improvements: ~10%
> > with
> > > > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and
> hopefully
> > > will
> > > > > merge these changes tomorrow.
> > > > >
> > > > > ​
> > > > >
> > > >
> > >
> >
>

Re: Branch deletion prohibited

[Yakov Zhdanov]

Disagree. This means none but committer can contribute.

--Yakov

2015-11-19 12:08 GMT+03:00 Raul Kripalani :

> I disagree.
>
> Code should be in the ASF infra.
>
> Pull requests make sense when outsiders want to make contributions.
>
> The usage of ASF infra is not a mere formality.
>
> Raúl.
> On 19 Nov 2015 08:57, "Yakov Zhdanov"  wrote:
>
> > Guys, therefore, let's develop new functionality in personal forks, test
> on
> > TC with pull requests and then merge to apache git as described here -
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >
> > We should create new branches only if this is really necessary.
> >
> > Thanks!
> > --
> > Yakov Zhdanov, Director R
> > *GridGain Systems*
> > www.gridgain.com
> >
> > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan :
> >
> > > Raul,
> > >
> > > ASF is currently prohibiting deletion of GIT branches until further
> > notice.
> > > Please add your branch to this Wiki page, so we don’t loose track:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > >
> > > Thanks,
> > > D.
> > >
> > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani 
> > wrote:
> > >
> > > > Fellows,
> > > >
> > > > I'm trying to push a branch deletion and the ASF Git tells me that
> > branch
> > > > deletion is prohibited.
> > > >
> > > > Has someone changed something?
> > > >
> > > > [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790
> > > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > error: failed to push some refs to '
> > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > >
> > > > Regards,
> > > >
> > > > *Raúl Kripalani*
> > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> > and
> > > > Messaging Engineer
> > > > http://about.me/raulkripalani |
> > http://www.linkedin.com/in/raulkripalani
> > > > http://blog.raulkr.net | twitter: @raulvk
> > > >
> > >
> >
>

Re: Branch deletion prohibited

[Raul Kripalani]

So branch deletion is disabled on purpose?
On 19 Nov 2015 09:10, "Artem Shutak"  wrote:

> Dmitriy,
>
> No, according to a note [1] on the wiki page [2] we need to check on
> unmerged changes before. Looks like we should add a status column (someone
> already has proposed it) where we can track is a branch ready to delete or
> not.
>
> [1] *Note. We don’t remove any *unmerged* branches. Even if the ticket was
> closed, it is possible that we forgot to merge. Before deleting a branch,
> we take an extra step to verify that the changes are in the master.*
> [2]
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
>
> -- Artem --
>
> On Thu, Nov 19, 2015 at 12:04 PM, Dmitriy Setrakyan  >
> wrote:
>
> > Should we file a ticket with INFRA asking them to delete all the branches
> > listed on this page:
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> >
> > Is it safe?
> >
> > D.
> >
> > On Thu, Nov 19, 2015 at 12:57 AM, Yakov Zhdanov 
> > wrote:
> >
> > > Guys, therefore, let's develop new functionality in personal forks,
> test
> > on
> > > TC with pull requests and then merge to apache git as described here -
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > >
> > > We should create new branches only if this is really necessary.
> > >
> > > Thanks!
> > > --
> > > Yakov Zhdanov, Director R
> > > *GridGain Systems*
> > > www.gridgain.com
> > >
> > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan :
> > >
> > > > Raul,
> > > >
> > > > ASF is currently prohibiting deletion of GIT branches until further
> > > notice.
> > > > Please add your branch to this Wiki page, so we don’t loose track:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > >
> > > > Thanks,
> > > > D.
> > > >
> > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani 
> > > wrote:
> > > >
> > > > > Fellows,
> > > > >
> > > > > I'm trying to push a branch deletion and the ASF Git tells me that
> > > branch
> > > > > deletion is prohibited.
> > > > >
> > > > > Has someone changed something?
> > > > >
> > > > > [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790
> > > > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > > error: failed to push some refs to '
> > > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > > >
> > > > > Regards,
> > > > >
> > > > > *Raúl Kripalani*
> > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> Data
> > > and
> > > > > Messaging Engineer
> > > > > http://about.me/raulkripalani |
> > > http://www.linkedin.com/in/raulkripalani
> > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > >
> > > >
> > >
> >
>

Re: Branch deletion prohibited

[Raul Kripalani]

Lads,

It is not clear to me whether branch deletion is prohibited ASF-wide
(Dmitriy: "we *cannot* delete branches") or by express project request.
I've understood both things from the thread. So let's wait for INFRA to
clarify: [1].

Can someone please explain why we resort to Github in the first place? Was
it for CI integration purposes?

Regards,

[1] https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-10798

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Nov 19, 2015 at 9:34 AM, Pavel Tupitsyn 
wrote:

> I'd like to add that there is virtually no difference between using a
> branch in original repo and a branch in your personal fork on GitHub.
> Merges and other operations work seamlessly between multiple remotes.
> Committers don't even have to create PRs (except to run a TC build).
>
> Thanks,
>
> On Thu, Nov 19, 2015 at 12:28 PM, Yakov Zhdanov 
> wrote:
>
> > But this leads to tons of garbage in repo and abandoned branches, etc.
> >
> > --Yakov
> >
> > 2015-11-19 12:19 GMT+03:00 Raul Kripalani :
> >
> > > As I said: "Pull requests make sense when outsiders want to make
> > > contributions."
> > >
> > > Committers with write access to ASF Git have no reason to develop in
> > > Github.
> > > On 19 Nov 2015 09:13, "Yakov Zhdanov"  wrote:
> > >
> > > > Disagree. This means none but committer can contribute.
> > > >
> > > > --Yakov
> > > >
> > > > 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
> > > >
> > > > > I disagree.
> > > > >
> > > > > Code should be in the ASF infra.
> > > > >
> > > > > Pull requests make sense when outsiders want to make contributions.
> > > > >
> > > > > The usage of ASF infra is not a mere formality.
> > > > >
> > > > > Raúl.
> > > > > On 19 Nov 2015 08:57, "Yakov Zhdanov" 
> wrote:
> > > > >
> > > > > > Guys, therefore, let's develop new functionality in personal
> forks,
> > > > test
> > > > > on
> > > > > > TC with pull requests and then merge to apache git as described
> > here
> > > -
> > > > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > > >
> > > > > > We should create new branches only if this is really necessary.
> > > > > >
> > > > > > Thanks!
> > > > > > --
> > > > > > Yakov Zhdanov, Director R
> > > > > > *GridGain Systems*
> > > > > > www.gridgain.com
> > > > > >
> > > > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >:
> > > > > >
> > > > > > > Raul,
> > > > > > >
> > > > > > > ASF is currently prohibiting deletion of GIT branches until
> > further
> > > > > > notice.
> > > > > > > Please add your branch to this Wiki page, so we don’t loose
> > track:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > > > > >
> > > > > > > Thanks,
> > > > > > > D.
> > > > > > >
> > > > > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani <
> > ra...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Fellows,
> > > > > > > >
> > > > > > > > I'm trying to push a branch deletion and the ASF Git tells me
> > > that
> > > > > > branch
> > > > > > > > deletion is prohibited.
> > > > > > > >
> > > > > > > > Has someone changed something?
> > > > > > > >
> > > > > > > > [raul@~/Workbench/Source/ignite$] git push -f origin
> > > :ignite-1790
> > > > > > > > remote: error: denying ref deletion for
> refs/heads/ignite-1790
> > > > > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > > > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > > > > > error: failed to push some refs to '
> > > > > > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > >
> > > > > > > > *Raúl Kripalani*
> > > > > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration,
> > Big
> > > > Data
> > > > > > and
> > > > > > > > Messaging Engineer
> > > > > > > > http://about.me/raulkripalani |
> > > > > > http://www.linkedin.com/in/raulkripalani
> > > > > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> --
> Pavel Tupitsyn
> GridGain Systems, Inc.
> www.gridgain.com
>

Ignite camel streamer

[Sergey Kozlov]

Hi Raul


I just found a few minor issues for your Ignite Camel streamer module if I
build the fabric edition:

1. The module has no README.txt (/libs/optional/ignite-camel/README.txt).
2. The module has no Apache License
(/libs/optional/ignite-camel/licenses/apache-2.0.txt).

Could you take a look and  fix it?

Thanks!

-- 
Sergey Kozlov

Re: Branch deletion prohibited

[Dmitriy Setrakyan]

Should we file a ticket with INFRA asking them to delete all the branches
listed on this page:
https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete

Is it safe?

D.

On Thu, Nov 19, 2015 at 12:57 AM, Yakov Zhdanov 
wrote:

> Guys, therefore, let's develop new functionality in personal forks, test on
> TC with pull requests and then merge to apache git as described here -
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> We should create new branches only if this is really necessary.
>
> Thanks!
> --
> Yakov Zhdanov, Director R
> *GridGain Systems*
> www.gridgain.com
>
> 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan :
>
> > Raul,
> >
> > ASF is currently prohibiting deletion of GIT branches until further
> notice.
> > Please add your branch to this Wiki page, so we don’t loose track:
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> >
> > Thanks,
> > D.
> >
> > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani 
> wrote:
> >
> > > Fellows,
> > >
> > > I'm trying to push a branch deletion and the ASF Git tells me that
> branch
> > > deletion is prohibited.
> > >
> > > Has someone changed something?
> > >
> > > [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790
> > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > To https://git-wip-us.apache.org/repos/asf/ignite
> > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > error: failed to push some refs to '
> > > https://git-wip-us.apache.org/repos/asf/ignite'
> > >
> > > Regards,
> > >
> > > *Raúl Kripalani*
> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> and
> > > Messaging Engineer
> > > http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> > > http://blog.raulkr.net | twitter: @raulvk
> > >
> >
>

Re: Branch deletion prohibited

[Raul Kripalani]

I disagree.

Code should be in the ASF infra.

Pull requests make sense when outsiders want to make contributions.

The usage of ASF infra is not a mere formality.

Raúl.
On 19 Nov 2015 08:57, "Yakov Zhdanov"  wrote:

> Guys, therefore, let's develop new functionality in personal forks, test on
> TC with pull requests and then merge to apache git as described here -
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> We should create new branches only if this is really necessary.
>
> Thanks!
> --
> Yakov Zhdanov, Director R
> *GridGain Systems*
> www.gridgain.com
>
> 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan :
>
> > Raul,
> >
> > ASF is currently prohibiting deletion of GIT branches until further
> notice.
> > Please add your branch to this Wiki page, so we don’t loose track:
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> >
> > Thanks,
> > D.
> >
> > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani 
> wrote:
> >
> > > Fellows,
> > >
> > > I'm trying to push a branch deletion and the ASF Git tells me that
> branch
> > > deletion is prohibited.
> > >
> > > Has someone changed something?
> > >
> > > [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790
> > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > To https://git-wip-us.apache.org/repos/asf/ignite
> > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > error: failed to push some refs to '
> > > https://git-wip-us.apache.org/repos/asf/ignite'
> > >
> > > Regards,
> > >
> > > *Raúl Kripalani*
> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> and
> > > Messaging Engineer
> > > http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> > > http://blog.raulkr.net | twitter: @raulvk
> > >
> >
>

Re: Branch deletion prohibited

[Dmitriy Setrakyan]

On Thu, Nov 19, 2015 at 1:19 AM, Raul Kripalani  wrote:

> As I said: "Pull requests make sense when outsiders want to make
> contributions."
>
> Committers with write access to ASF Git have no reason to develop
> in Github.
>

Raul, given that we cannot delete branches, I think we should very closely
look at the GitHub PRs even for committers. Many committers prefer Github
PR process instead of submitting patches.


> On 19 Nov 2015 09:13, "Yakov Zhdanov"  wrote:
>
> > Disagree. This means none but committer can contribute.
> >
> > --Yakov
> >
> > 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
> >
> > > I disagree.
> > >
> > > Code should be in the ASF infra.
> > >
> > > Pull requests make sense when outsiders want to make contributions.
> > >
> > > The usage of ASF infra is not a mere formality.
> > >
> > > Raúl.
> > > On 19 Nov 2015 08:57, "Yakov Zhdanov"  wrote:
> > >
> > > > Guys, therefore, let's develop new functionality in personal forks,
> > test
> > > on
> > > > TC with pull requests and then merge to apache git as described here
> -
> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > >
> > > > We should create new branches only if this is really necessary.
> > > >
> > > > Thanks!
> > > > --
> > > > Yakov Zhdanov, Director R
> > > > *GridGain Systems*
> > > > www.gridgain.com
> > > >
> > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan  >:
> > > >
> > > > > Raul,
> > > > >
> > > > > ASF is currently prohibiting deletion of GIT branches until further
> > > > notice.
> > > > > Please add your branch to this Wiki page, so we don’t loose track:
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > > >
> > > > > Thanks,
> > > > > D.
> > > > >
> > > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani  >
> > > > wrote:
> > > > >
> > > > > > Fellows,
> > > > > >
> > > > > > I'm trying to push a branch deletion and the ASF Git tells me
> that
> > > > branch
> > > > > > deletion is prohibited.
> > > > > >
> > > > > > Has someone changed something?
> > > > > >
> > > > > > [raul@~/Workbench/Source/ignite$] git push -f origin
> :ignite-1790
> > > > > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > > > error: failed to push some refs to '
> > > > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > *Raúl Kripalani*
> > > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> > Data
> > > > and
> > > > > > Messaging Engineer
> > > > > > http://about.me/raulkripalani |
> > > > http://www.linkedin.com/in/raulkripalani
> > > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Branch deletion prohibited

[Pavel Tupitsyn]

I'd like to add that there is virtually no difference between using a
branch in original repo and a branch in your personal fork on GitHub.
Merges and other operations work seamlessly between multiple remotes.
Committers don't even have to create PRs (except to run a TC build).

Thanks,

On Thu, Nov 19, 2015 at 12:28 PM, Yakov Zhdanov  wrote:

> But this leads to tons of garbage in repo and abandoned branches, etc.
>
> --Yakov
>
> 2015-11-19 12:19 GMT+03:00 Raul Kripalani :
>
> > As I said: "Pull requests make sense when outsiders want to make
> > contributions."
> >
> > Committers with write access to ASF Git have no reason to develop in
> > Github.
> > On 19 Nov 2015 09:13, "Yakov Zhdanov"  wrote:
> >
> > > Disagree. This means none but committer can contribute.
> > >
> > > --Yakov
> > >
> > > 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
> > >
> > > > I disagree.
> > > >
> > > > Code should be in the ASF infra.
> > > >
> > > > Pull requests make sense when outsiders want to make contributions.
> > > >
> > > > The usage of ASF infra is not a mere formality.
> > > >
> > > > Raúl.
> > > > On 19 Nov 2015 08:57, "Yakov Zhdanov"  wrote:
> > > >
> > > > > Guys, therefore, let's develop new functionality in personal forks,
> > > test
> > > > on
> > > > > TC with pull requests and then merge to apache git as described
> here
> > -
> > > > >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > >
> > > > > We should create new branches only if this is really necessary.
> > > > >
> > > > > Thanks!
> > > > > --
> > > > > Yakov Zhdanov, Director R
> > > > > *GridGain Systems*
> > > > > www.gridgain.com
> > > > >
> > > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >:
> > > > >
> > > > > > Raul,
> > > > > >
> > > > > > ASF is currently prohibiting deletion of GIT branches until
> further
> > > > > notice.
> > > > > > Please add your branch to this Wiki page, so we don’t loose
> track:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > > > >
> > > > > > Thanks,
> > > > > > D.
> > > > > >
> > > > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani <
> ra...@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Fellows,
> > > > > > >
> > > > > > > I'm trying to push a branch deletion and the ASF Git tells me
> > that
> > > > > branch
> > > > > > > deletion is prohibited.
> > > > > > >
> > > > > > > Has someone changed something?
> > > > > > >
> > > > > > > [raul@~/Workbench/Source/ignite$] git push -f origin
> > :ignite-1790
> > > > > > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > > > > error: failed to push some refs to '
> > > > > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > *Raúl Kripalani*
> > > > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration,
> Big
> > > Data
> > > > > and
> > > > > > > Messaging Engineer
> > > > > > > http://about.me/raulkripalani |
> > > > > http://www.linkedin.com/in/raulkripalani
> > > > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>



-- 
-- 
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com

Re: Javadoc warnings at Ignite 1.5

[Sergey Kozlov]

Hi

Thanks Anton for updating the wiki.

I faced same issues during last 2-3 months and would be nice to avoid them
in future

On Thu, Nov 19, 2015 at 12:37 PM, Anton Vinogradov  wrote:

> Raul,
>
> Of course I can,
> But this changes made by you recently, and it will be nice if you'll fix
> them.
>
> I've added some requirment to
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> Please see section Checklist before pust
> <
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepust
> >
> .
>
> On Thu, Nov 19, 2015 at 12:06 PM, Raul Kripalani  wrote:
>
> > Anton,
> >
> > Could you please just go ahead and fix it? This is a collaborative
> > project. Source is not owned by individual people.
> >
> > And let's not abuse the mailing list for details like this.
> >
> > Regards,
> > Raúl.
> > On 19 Nov 2015 08:49, "Anton Vinogradov" 
> wrote:
> >
> >> Hello,
> >>
> >> I've checked output of prerelease build of Ignite 1.5 and found javadoc
> >> warnings like
> >> CamelStreamer.java:51: warning - Tag @link: malformed:
> >> "StreamMultipleTupleExtractor)"
> >>
> >> Raul, seems that was your changes. Could you please fix it?
> >>
> >
>



-- 
Sergey Kozlov

Re: Branch deletion prohibited

[Dmitriy Setrakyan]

On Thu, Nov 19, 2015 at 1:41 AM, Raul Kripalani  wrote:

> On Thu, Nov 19, 2015 at 9:28 AM, Yakov Zhdanov 
> wrote:
>
> > But this leads to tons of garbage in repo and abandoned branches, etc.
> >
>
> "Let's not do X because our developers are irresponsible and leave branches
> behind?" -- Really? We have a zillion-pages set of contribution guidelines
> and we still think our developers are any liberty?
>
> Let's just add one more section to Coding guidelines about branch
> lifecycle, if that's what you're worried about.
>

Raul, we physically cannot delete branches. ASF GIT does not allow it.


>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>

Re: Branch deletion prohibited

[Vladimir Ozerov]

I agree that there is absolutely no problems of have multiple ways to
provide contributions.

If you are contributor, you can:
- Provide a patch;
- Provide a PR using GitHub mirror.

If you are committer, you can:
- Provide a patch;
- Provide a PR using GitHub mirror;
- Use branch in ASF repo and remove it in the end.

ASF branches removal is temporary restricted by INFRA. As soon as it is
enabled again why not using it? It is the easiest way to provide
contributions and review them.

On Thu, Nov 19, 2015 at 12:49 PM, Raul Kripalani  wrote:

> Lads,
>
> It is not clear to me whether branch deletion is prohibited ASF-wide
> (Dmitriy: "we *cannot* delete branches") or by express project request.
> I've understood both things from the thread. So let's wait for INFRA to
> clarify: [1].
>
> Can someone please explain why we resort to Github in the first place? Was
> it for CI integration purposes?
>
> Regards,
>
> [1]
> https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-10798
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Thu, Nov 19, 2015 at 9:34 AM, Pavel Tupitsyn 
> wrote:
>
> > I'd like to add that there is virtually no difference between using a
> > branch in original repo and a branch in your personal fork on GitHub.
> > Merges and other operations work seamlessly between multiple remotes.
> > Committers don't even have to create PRs (except to run a TC build).
> >
> > Thanks,
> >
> > On Thu, Nov 19, 2015 at 12:28 PM, Yakov Zhdanov 
> > wrote:
> >
> > > But this leads to tons of garbage in repo and abandoned branches, etc.
> > >
> > > --Yakov
> > >
> > > 2015-11-19 12:19 GMT+03:00 Raul Kripalani :
> > >
> > > > As I said: "Pull requests make sense when outsiders want to make
> > > > contributions."
> > > >
> > > > Committers with write access to ASF Git have no reason to develop in
> > > > Github.
> > > > On 19 Nov 2015 09:13, "Yakov Zhdanov"  wrote:
> > > >
> > > > > Disagree. This means none but committer can contribute.
> > > > >
> > > > > --Yakov
> > > > >
> > > > > 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
> > > > >
> > > > > > I disagree.
> > > > > >
> > > > > > Code should be in the ASF infra.
> > > > > >
> > > > > > Pull requests make sense when outsiders want to make
> contributions.
> > > > > >
> > > > > > The usage of ASF infra is not a mere formality.
> > > > > >
> > > > > > Raúl.
> > > > > > On 19 Nov 2015 08:57, "Yakov Zhdanov" 
> > wrote:
> > > > > >
> > > > > > > Guys, therefore, let's develop new functionality in personal
> > forks,
> > > > > test
> > > > > > on
> > > > > > > TC with pull requests and then merge to apache git as described
> > > here
> > > > -
> > > > > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > > > >
> > > > > > > We should create new branches only if this is really necessary.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > --
> > > > > > > Yakov Zhdanov, Director R
> > > > > > > *GridGain Systems*
> > > > > > > www.gridgain.com
> > > > > > >
> > > > > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > > > >:
> > > > > > >
> > > > > > > > Raul,
> > > > > > > >
> > > > > > > > ASF is currently prohibiting deletion of GIT branches until
> > > further
> > > > > > > notice.
> > > > > > > > Please add your branch to this Wiki page, so we don’t loose
> > > track:
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani <
> > > ra...@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Fellows,
> > > > > > > > >
> > > > > > > > > I'm trying to push a branch deletion and the ASF Git tells
> me
> > > > that
> > > > > > > branch
> > > > > > > > > deletion is prohibited.
> > > > > > > > >
> > > > > > > > > Has someone changed something?
> > > > > > > > >
> > > > > > > > > [raul@~/Workbench/Source/ignite$] git push -f origin
> > > > :ignite-1790
> > > > > > > > > remote: error: denying ref deletion for
> > refs/heads/ignite-1790
> > > > > > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > > > > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > > > > > > error: failed to push some refs to '
> > > > > > > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > >
> > > > > > > > > *Raúl Kripalani*
> > > > > > > > > PMC & Committer @ Apache Ignite, Apache Camel |
> Integration,
> > > Big
> > > > > Data
> > > 

Re: Ignite-1.5 Release

[Raul Kripalani]

The code was already reviewed and merged with squash. IGNITE-1790.
On 19 Nov 2015 08:30, "Romain Gilles"  wrote:

> Hi Raul,
> Could you please give the pull request or the branch or the ignite ticket
> number?
> I will be please to have a look to your pull request.
>
> Thanks,
>
> Romain
>
> Le jeu. 19 nov. 2015 à 04:01, Dmitriy Setrakyan  a
> écrit :
>
> > On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani 
> wrote:
> >
> > > I merged the Camel Streamer today and I hope to finish the first phase
> of
> > > OSGi tomorrow.
> > >
> > > I'll need someone to review the latter quickly if we want it merged for
> > > 1.5... No code changes in existing codebase. Just a new osgi module and
> > > many POM changes mainly to generate the manifests.
> > >
> >
> > Raul, did you create a patch or a PR? I can’t find it anywhere.
> >
> >
> > >
> > > Should be a quick task.
> > >
> > > Regards,
> > > Raúl.
> > > On 18 Nov 2015 20:38, "Vladimir Ozerov"  wrote:
> > >
> > > > Hi Alex,
> > > >
> > > > Today I marged several big things into 1282 - reworked metadat and
> > > > compacted footers optimization. I have on big ticket left -
> > IGNITE-1917 -
> > > > with marshalling microoptimizations. They should not conflict with
> > > anything
> > > > and I expect them to be finalized tomorrow. All optimizations are
> > ready,
> > > I
> > > > just need to perform some cleanup and refactoring.
> > > >
> > > > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > > > alexey.goncha...@gmail.com> wrote:
> > > >
> > > > > Hi folks,
> > > > >
> > > > > I merged performance optimizations for tx mode which gave up to 5%
> > > > > improvement for tx-put benchmark to ignite-1.5.
> > > > >
> > > > > I also pushed finalizaing changes to Binary configuration in
> > > ignite-1945
> > > > > branch and currently waiting for TC. If all is ok, will cooperate
> > with
> > > > > Vladimir Ozerov and merge changes tomorrow.
> > > > >
> > > > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov :
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Yesterday I merged optimizations for tx update operations working
> > > > single
> > > > > > key, got ~7% improvement in tx-put benchmark.
> > > > > >
> > > > > > And today I finished to implement optimization for cache 'get'
> > > > operation
> > > > > > with single key. Got another benchmark results improvements: ~10%
> > > with
> > > > > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and
> > hopefully
> > > > will
> > > > > > merge these changes tomorrow.
> > > > > >
> > > > > > ​
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Branch deletion prohibited

[Raul Kripalani]

As I said: "Pull requests make sense when outsiders want to make
contributions."

Committers with write access to ASF Git have no reason to develop in
Github.
On 19 Nov 2015 09:13, "Yakov Zhdanov"  wrote:

> Disagree. This means none but committer can contribute.
>
> --Yakov
>
> 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
>
> > I disagree.
> >
> > Code should be in the ASF infra.
> >
> > Pull requests make sense when outsiders want to make contributions.
> >
> > The usage of ASF infra is not a mere formality.
> >
> > Raúl.
> > On 19 Nov 2015 08:57, "Yakov Zhdanov"  wrote:
> >
> > > Guys, therefore, let's develop new functionality in personal forks,
> test
> > on
> > > TC with pull requests and then merge to apache git as described here -
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > >
> > > We should create new branches only if this is really necessary.
> > >
> > > Thanks!
> > > --
> > > Yakov Zhdanov, Director R
> > > *GridGain Systems*
> > > www.gridgain.com
> > >
> > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan :
> > >
> > > > Raul,
> > > >
> > > > ASF is currently prohibiting deletion of GIT branches until further
> > > notice.
> > > > Please add your branch to this Wiki page, so we don’t loose track:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > >
> > > > Thanks,
> > > > D.
> > > >
> > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani 
> > > wrote:
> > > >
> > > > > Fellows,
> > > > >
> > > > > I'm trying to push a branch deletion and the ASF Git tells me that
> > > branch
> > > > > deletion is prohibited.
> > > > >
> > > > > Has someone changed something?
> > > > >
> > > > > [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790
> > > > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > > error: failed to push some refs to '
> > > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > > >
> > > > > Regards,
> > > > >
> > > > > *Raúl Kripalani*
> > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> Data
> > > and
> > > > > Messaging Engineer
> > > > > http://about.me/raulkripalani |
> > > http://www.linkedin.com/in/raulkripalani
> > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > >
> > > >
> > >
> >
>

Re: Branch deletion prohibited

[Yakov Zhdanov]

But this leads to tons of garbage in repo and abandoned branches, etc.

--Yakov

2015-11-19 12:19 GMT+03:00 Raul Kripalani :

> As I said: "Pull requests make sense when outsiders want to make
> contributions."
>
> Committers with write access to ASF Git have no reason to develop in
> Github.
> On 19 Nov 2015 09:13, "Yakov Zhdanov"  wrote:
>
> > Disagree. This means none but committer can contribute.
> >
> > --Yakov
> >
> > 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
> >
> > > I disagree.
> > >
> > > Code should be in the ASF infra.
> > >
> > > Pull requests make sense when outsiders want to make contributions.
> > >
> > > The usage of ASF infra is not a mere formality.
> > >
> > > Raúl.
> > > On 19 Nov 2015 08:57, "Yakov Zhdanov"  wrote:
> > >
> > > > Guys, therefore, let's develop new functionality in personal forks,
> > test
> > > on
> > > > TC with pull requests and then merge to apache git as described here
> -
> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > >
> > > > We should create new branches only if this is really necessary.
> > > >
> > > > Thanks!
> > > > --
> > > > Yakov Zhdanov, Director R
> > > > *GridGain Systems*
> > > > www.gridgain.com
> > > >
> > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan  >:
> > > >
> > > > > Raul,
> > > > >
> > > > > ASF is currently prohibiting deletion of GIT branches until further
> > > > notice.
> > > > > Please add your branch to this Wiki page, so we don’t loose track:
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > > >
> > > > > Thanks,
> > > > > D.
> > > > >
> > > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani  >
> > > > wrote:
> > > > >
> > > > > > Fellows,
> > > > > >
> > > > > > I'm trying to push a branch deletion and the ASF Git tells me
> that
> > > > branch
> > > > > > deletion is prohibited.
> > > > > >
> > > > > > Has someone changed something?
> > > > > >
> > > > > > [raul@~/Workbench/Source/ignite$] git push -f origin
> :ignite-1790
> > > > > > remote: error: denying ref deletion for refs/heads/ignite-1790
> > > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > > >  ! [remote rejected] ignite-1790 (deletion prohibited)
> > > > > > error: failed to push some refs to '
> > > > > > https://git-wip-us.apache.org/repos/asf/ignite'
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > *Raúl Kripalani*
> > > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> > Data
> > > > and
> > > > > > Messaging Engineer
> > > > > > http://about.me/raulkripalani |
> > > > http://www.linkedin.com/in/raulkripalani
> > > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Javadoc warnings at Ignite 1.5

[Anton Vinogradov]

Raul,

Of course I can,
But this changes made by you recently, and it will be nice if you'll fix
them.

I've added some requirment to
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Please see section Checklist before pust

.

On Thu, Nov 19, 2015 at 12:06 PM, Raul Kripalani  wrote:

> Anton,
>
> Could you please just go ahead and fix it? This is a collaborative
> project. Source is not owned by individual people.
>
> And let's not abuse the mailing list for details like this.
>
> Regards,
> Raúl.
> On 19 Nov 2015 08:49, "Anton Vinogradov"  wrote:
>
>> Hello,
>>
>> I've checked output of prerelease build of Ignite 1.5 and found javadoc
>> warnings like
>> CamelStreamer.java:51: warning - Tag @link: malformed:
>> "StreamMultipleTupleExtractor)"
>>
>> Raul, seems that was your changes. Could you please fix it?
>>
>

Re: Branch deletion prohibited

[Raul Kripalani]

On Thu, Nov 19, 2015 at 9:28 AM, Yakov Zhdanov  wrote:

> But this leads to tons of garbage in repo and abandoned branches, etc.
>

"Let's not do X because our developers are irresponsible and leave branches
behind?" -- Really? We have a zillion-pages set of contribution guidelines
and we still think our developers are any liberty?

Let's just add one more section to Coding guidelines about branch
lifecycle, if that's what you're worried about.

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

[jira] [Created] (IGNITE-1949) C++ platform library for Linux: make uninstall doesn't delete directories

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-1949:
---

 Summary: C++ platform library for Linux: make uninstall doesn't 
delete directories
 Key: IGNITE-1949
 URL: https://issues.apache.org/jira/browse/IGNITE-1949
 Project: Ignite
  Issue Type: Bug
Affects Versions: ignite-1.4
Reporter: Igor Sapego
Assignee: Igor Sapego
Priority: Minor


Uninstall doesn't delete directories created for include files




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: Ignite 1510

[iveselovskiy]

GitHub user iveselovskiy opened a pull request:

https://github.com/apache/ignite/pull/249

Ignite 1510



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/iveselovskiy/ignite ignite-1510

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/249.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #249


commit f7a08b5968e3d8345bdab09477b44acccb1e06c4
Author: iveselovskiy 
Date:   2015-11-16T18:38:01Z

ignite-1639

commit 267e8a5a60b623c8dced0ddee98169c39ed8bff0
Author: iveselovskiy 
Date:   2015-11-18T13:27:22Z

Merge branch 'master' of https://github.com/apache/ignite

commit 8e40dad2be34f93f52f3386d3ad468485b34edfa
Author: iveselovskiy 
Date:   2015-11-19T18:28:50Z

ignite-1510




---
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.
---

Re: Ignite-1.5 Release

[Raul Kripalani]

Can someone please clarify the *exact* release schedule?

I hear that the merges may be completed tomorrow Friday, but the release
will be built next Friday. Is this correct?

I'm finishing my work on the OSGi integration (three modules), which I'd
like to get into 1.5. I'm pretty much done, and I'm just finishing
Javadocs, README, etc.

I also want to create 2 unit tests for the two different classloading
strategies I've built, but it'll require a bit of fiddling with Pax Exam
and TinyBundles.

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Nov 19, 2015 at 2:29 PM, Yakov Zhdanov  wrote:

> Hey guys!
>
> We are getting closer to the release! Thanks to everyone making this
> closer!
>
> Let's update status info.
>
> My understanding is that the following major parts are still not merged.
> Can everyone mentioned provide ticket number(s) and estimates on when the
> functionality will be merged.
>
> 1. Data grid performance optimizations: single get/put - Semyon
> 2. Direct marshalling compactions: communication optimization - Valentin
> 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
> 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
>
> Thanks!
>
> --Yakov
>

Re: Ignite-1.5 Release

[Nikolay Tikhonov]

I've merged changes related to IGNITE-426 (Make sure continuous queries
notifications are not missed in case primary node fails
) task.

On Thu, Nov 19, 2015 at 5:53 PM, Anton Vinogradov 
wrote:

> Twitter intergration
> *https://issues.apache.org/jira/browse/IGNITE-530
> *
>
> is done too
>
> On Thu, Nov 19, 2015 at 5:32 PM, Semyon Boikov 
> wrote:
>
> > Just merged single get optimizations (improvements in the last benchmarks
> > run: ~10% for atomic-put-get, ~5% for tx-put-get).
> >
>

[jira] [Created] (IGNITE-1956) Portable object requires to have a class to get Enum field value

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-1956:
---

 Summary: Portable object requires to have a class to get Enum 
field value
 Key: IGNITE-1956
 URL: https://issues.apache.org/jira/browse/IGNITE-1956
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Valentin Kulichenko
 Fix For: 1.6


{{PortableObject.field()}} method implementation attempts to resolve the class 
if the field type is Enum. This is wrong, because this method should work on 
server side without classes on classpath. Also this breaks the {{toString()}} 
method in this case.

In addition, .NET always writes {{-1}} as a type ID for any enum, so on Java 
side it is resolved into {{java.lang.Object}}. As a result, {{field()}} and 
{{toString()} method fail with this exception:
{code}
Caused by: org.apache.ignite.internal.portable.api.PortableException: Class 
does not represent enum type: java.lang.Object
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1953) PortableContext: rework ID mappers handling.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1953:
---

 Summary: PortableContext: rework ID mappers handling.
 Key: IGNITE-1953
 URL: https://issues.apache.org/jira/browse/IGNITE-1953
 Project: Ignite
  Issue Type: Bug
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


1) BasicClassIdMapper.typeId do not perform to-lower-case conversion.
2) BasicClassIdMapper appears to behave in absolutely the same way as 
IdMapperWrapper(null). Then why do we have two constants DFLT_ID_MAPPER and 
BASIC_CLS_ID_MAPPER?
3) We can slightly improve perofrmance introducing internal ID mapper with two 
implementations - default (lower case hash code) and delegating (will 
user-supplied mapper). This way we will reduce amount of virtual calls in the 
most common case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Javadoc warnings at Ignite 1.5

[Raul Kripalani]

Anton, fixed in ignite-1.5.

You said "warnings" in plural, but I only found the one. Could you clarify
where else?

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Nov 19, 2015 at 9:37 AM, Anton Vinogradov 
wrote:

> Raul,
>
> Of course I can,
> But this changes made by you recently, and it will be nice if you'll fix
> them.
>
> I've added some requirment to
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> Please see section Checklist before pust
> <
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepust
> >
> .
>
> On Thu, Nov 19, 2015 at 12:06 PM, Raul Kripalani  wrote:
>
> > Anton,
> >
> > Could you please just go ahead and fix it? This is a collaborative
> > project. Source is not owned by individual people.
> >
> > And let's not abuse the mailing list for details like this.
> >
> > Regards,
> > Raúl.
> > On 19 Nov 2015 08:49, "Anton Vinogradov" 
> wrote:
> >
> >> Hello,
> >>
> >> I've checked output of prerelease build of Ignite 1.5 and found javadoc
> >> warnings like
> >> CamelStreamer.java:51: warning - Tag @link: malformed:
> >> "StreamMultipleTupleExtractor)"
> >>
> >> Raul, seems that was your changes. Could you please fix it?
> >>
> >
>

Re: Branch deletion prohibited

[Raul Kripalani]

Ok. So Infra replied and referred to an email on November 3rd which I
somehow missed, indicating that it is indeed an ASF-wide temporary
restriction.

+1 to liberty of options to contribute/commit and to temporarily keeping
track of branches to delete in the Wiki.

Regards,

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Nov 19, 2015 at 10:21 AM, Semyon Boikov 
wrote:

> +1
>
> On Thu, Nov 19, 2015 at 1:07 PM, Vladimir Ozerov 
> wrote:
>
> > I agree that there is absolutely no problems of have multiple ways to
> > provide contributions.
> >
> > If you are contributor, you can:
> > - Provide a patch;
> > - Provide a PR using GitHub mirror.
> >
> > If you are committer, you can:
> > - Provide a patch;
> > - Provide a PR using GitHub mirror;
> > - Use branch in ASF repo and remove it in the end.
> >
> > ASF branches removal is temporary restricted by INFRA. As soon as it is
> > enabled again why not using it? It is the easiest way to provide
> > contributions and review them.
> >
> > On Thu, Nov 19, 2015 at 12:49 PM, Raul Kripalani 
> wrote:
> >
> > > Lads,
> > >
> > > It is not clear to me whether branch deletion is prohibited ASF-wide
> > > (Dmitriy: "we *cannot* delete branches") or by express project request.
> > > I've understood both things from the thread. So let's wait for INFRA to
> > > clarify: [1].
> > >
> > > Can someone please explain why we resort to Github in the first place?
> > Was
> > > it for CI integration purposes?
> > >
> > > Regards,
> > >
> > > [1]
> > >
> https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-10798
> > >
> > > *Raúl Kripalani*
> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> and
> > > Messaging Engineer
> > > http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> > > http://blog.raulkr.net | twitter: @raulvk
> > >
> > > On Thu, Nov 19, 2015 at 9:34 AM, Pavel Tupitsyn <
> ptupit...@gridgain.com>
> > > wrote:
> > >
> > > > I'd like to add that there is virtually no difference between using a
> > > > branch in original repo and a branch in your personal fork on GitHub.
> > > > Merges and other operations work seamlessly between multiple remotes.
> > > > Committers don't even have to create PRs (except to run a TC build).
> > > >
> > > > Thanks,
> > > >
> > > > On Thu, Nov 19, 2015 at 12:28 PM, Yakov Zhdanov  >
> > > > wrote:
> > > >
> > > > > But this leads to tons of garbage in repo and abandoned branches,
> > etc.
> > > > >
> > > > > --Yakov
> > > > >
> > > > > 2015-11-19 12:19 GMT+03:00 Raul Kripalani :
> > > > >
> > > > > > As I said: "Pull requests make sense when outsiders want to make
> > > > > > contributions."
> > > > > >
> > > > > > Committers with write access to ASF Git have no reason to develop
> > in
> > > > > > Github.
> > > > > > On 19 Nov 2015 09:13, "Yakov Zhdanov" 
> wrote:
> > > > > >
> > > > > > > Disagree. This means none but committer can contribute.
> > > > > > >
> > > > > > > --Yakov
> > > > > > >
> > > > > > > 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
> > > > > > >
> > > > > > > > I disagree.
> > > > > > > >
> > > > > > > > Code should be in the ASF infra.
> > > > > > > >
> > > > > > > > Pull requests make sense when outsiders want to make
> > > contributions.
> > > > > > > >
> > > > > > > > The usage of ASF infra is not a mere formality.
> > > > > > > >
> > > > > > > > Raúl.
> > > > > > > > On 19 Nov 2015 08:57, "Yakov Zhdanov"  >
> > > > wrote:
> > > > > > > >
> > > > > > > > > Guys, therefore, let's develop new functionality in
> personal
> > > > forks,
> > > > > > > test
> > > > > > > > on
> > > > > > > > > TC with pull requests and then merge to apache git as
> > described
> > > > > here
> > > > > > -
> > > > > > > > >
> > > > >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > > > > > >
> > > > > > > > > We should create new branches only if this is really
> > necessary.
> > > > > > > > >
> > > > > > > > > Thanks!
> > > > > > > > > --
> > > > > > > > > Yakov Zhdanov, Director R
> > > > > > > > > *GridGain Systems*
> > > > > > > > > www.gridgain.com
> > > > > > > > >
> > > > > > > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan <
> > > > > dsetrak...@apache.org
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > Raul,
> > > > > > > > > >
> > > > > > > > > > ASF is currently prohibiting deletion of GIT branches
> until
> > > > > further
> > > > > > > > > notice.
> > > > > > > > > > Please add your branch to this Wiki page, so we don’t
> loose
> > > > > track:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> 

[GitHub] ignite pull request: IGNITE-1949: Linux: make uninstall now delete...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/247

IGNITE-1949: Linux: make uninstall now delete directories.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-1949

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/247.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #247


commit 2b554dfb8e5ffec3a6ae707f725a633ff373b499
Author: Igor Sapego 
Date:   2015-11-19T10:13:47Z

IGNITE-1949: C++ platform library for Linux: make uninstall now delete 
directories.




---
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.
---

Re: Branch deletion prohibited

[Semyon Boikov]

+1

On Thu, Nov 19, 2015 at 1:07 PM, Vladimir Ozerov 
wrote:

> I agree that there is absolutely no problems of have multiple ways to
> provide contributions.
>
> If you are contributor, you can:
> - Provide a patch;
> - Provide a PR using GitHub mirror.
>
> If you are committer, you can:
> - Provide a patch;
> - Provide a PR using GitHub mirror;
> - Use branch in ASF repo and remove it in the end.
>
> ASF branches removal is temporary restricted by INFRA. As soon as it is
> enabled again why not using it? It is the easiest way to provide
> contributions and review them.
>
> On Thu, Nov 19, 2015 at 12:49 PM, Raul Kripalani  wrote:
>
> > Lads,
> >
> > It is not clear to me whether branch deletion is prohibited ASF-wide
> > (Dmitriy: "we *cannot* delete branches") or by express project request.
> > I've understood both things from the thread. So let's wait for INFRA to
> > clarify: [1].
> >
> > Can someone please explain why we resort to Github in the first place?
> Was
> > it for CI integration purposes?
> >
> > Regards,
> >
> > [1]
> > https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-10798
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Thu, Nov 19, 2015 at 9:34 AM, Pavel Tupitsyn 
> > wrote:
> >
> > > I'd like to add that there is virtually no difference between using a
> > > branch in original repo and a branch in your personal fork on GitHub.
> > > Merges and other operations work seamlessly between multiple remotes.
> > > Committers don't even have to create PRs (except to run a TC build).
> > >
> > > Thanks,
> > >
> > > On Thu, Nov 19, 2015 at 12:28 PM, Yakov Zhdanov 
> > > wrote:
> > >
> > > > But this leads to tons of garbage in repo and abandoned branches,
> etc.
> > > >
> > > > --Yakov
> > > >
> > > > 2015-11-19 12:19 GMT+03:00 Raul Kripalani :
> > > >
> > > > > As I said: "Pull requests make sense when outsiders want to make
> > > > > contributions."
> > > > >
> > > > > Committers with write access to ASF Git have no reason to develop
> in
> > > > > Github.
> > > > > On 19 Nov 2015 09:13, "Yakov Zhdanov"  wrote:
> > > > >
> > > > > > Disagree. This means none but committer can contribute.
> > > > > >
> > > > > > --Yakov
> > > > > >
> > > > > > 2015-11-19 12:08 GMT+03:00 Raul Kripalani :
> > > > > >
> > > > > > > I disagree.
> > > > > > >
> > > > > > > Code should be in the ASF infra.
> > > > > > >
> > > > > > > Pull requests make sense when outsiders want to make
> > contributions.
> > > > > > >
> > > > > > > The usage of ASF infra is not a mere formality.
> > > > > > >
> > > > > > > Raúl.
> > > > > > > On 19 Nov 2015 08:57, "Yakov Zhdanov" 
> > > wrote:
> > > > > > >
> > > > > > > > Guys, therefore, let's develop new functionality in personal
> > > forks,
> > > > > > test
> > > > > > > on
> > > > > > > > TC with pull requests and then merge to apache git as
> described
> > > > here
> > > > > -
> > > > > > > >
> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > > > > >
> > > > > > > > We should create new branches only if this is really
> necessary.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > > --
> > > > > > > > Yakov Zhdanov, Director R
> > > > > > > > *GridGain Systems*
> > > > > > > > www.gridgain.com
> > > > > > > >
> > > > > > > > 2015-11-18 23:04 GMT+03:00 Dmitriy Setrakyan <
> > > > dsetrak...@apache.org
> > > > > >:
> > > > > > > >
> > > > > > > > > Raul,
> > > > > > > > >
> > > > > > > > > ASF is currently prohibiting deletion of GIT branches until
> > > > further
> > > > > > > > notice.
> > > > > > > > > Please add your branch to this Wiki page, so we don’t loose
> > > > track:
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani <
> > > > ra...@apache.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Fellows,
> > > > > > > > > >
> > > > > > > > > > I'm trying to push a branch deletion and the ASF Git
> tells
> > me
> > > > > that
> > > > > > > > branch
> > > > > > > > > > deletion is prohibited.
> > > > > > > > > >
> > > > > > > > > > Has someone changed something?
> > > > > > > > > >
> > > > > > > > > > [raul@~/Workbench/Source/ignite$] git push -f origin
> > > > > :ignite-1790
> > > > > > > > > > remote: error: denying ref deletion for
> > > refs/heads/ignite-1790
> > > > > > > > > > To https://git-wip-us.apache.org/repos/asf/ignite
> > > > > > > > > > 

[GitHub] ignite pull request: ignite-1955 ACCEPT_ALL predicate should have ...

[agura]

GitHub user agura opened a pull request:

https://github.com/apache/ignite/pull/248

ignite-1955 ACCEPT_ALL predicate should have SUID



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/agura/incubator-ignite ignite-1955

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/248.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #248


commit e70163edd679d8531fd7ff86c964bf8ab7882558
Author: agura 
Date:   2015-11-19T16:19:27Z

ignite-1955 ACCEPT_ALL predicate should have SUID




---
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] [Created] (IGNITE-1955) ACCEPT_ALL predicate should have SUID

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-1955:
---

 Summary: ACCEPT_ALL predicate should have SUID
 Key: IGNITE-1955
 URL: https://issues.apache.org/jira/browse/IGNITE-1955
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Gura
Assignee: Andrey Gura
 Fix For: 1.5


{{IgniteCacheProxy.ACCEPT_ALL}} should have {{serialVersionUID}} field because 
scan query without filter can fail in cluster with different JVM vendors.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Javadoc warnings at Ignite 1.5

[Raul Kripalani]

The culprit was just a single parenthesis in the Javadoc tag, Anton.

StreamMultipleTupleExtractor*)*

Anton, as I said, the code is not copyrighted by me. It belongs to the
community.

You are a committer and a PMC member in this project. Please just feel free
to improve the code/docs whenever you want to.

It is absurd to _play Police_, an absolute *overkill*, an utter *waste* of
everybody's time and an *abuse* of the dev@ mailing list.

We have already typed 1000s of characters in emails just to fix a single
one.

Let's discuss this in the private@ list.

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Nov 19, 2015 at 12:45 PM, Anton Vinogradov  wrote:

> Raul,
>
> [10:19:42]W: [org.apache.ignite:ignite-camel] [WARNING]
>
> /home/teamcity/TeamCityAgent/work/1217c33bbef63537/incubator-ignite/modules/camel/src/main/java/org/apache/ignite/stream/camel/CamelStreamer.java:51:
> warning - Tag @link: malformed: "StreamMultipleTupleExtractor)"
> [10:19:42]W: [org.apache.ignite:ignite-camel] [WARNING]
>
> /home/teamcity/TeamCityAgent/work/1217c33bbef63537/incubator-ignite/modules/camel/src/main/java/org/apache/ignite/stream/camel/CamelStreamer.java:51:
> warning - Tag @link: reference not found: StreamMultipleTupleExtractor)
>
> On Thu, Nov 19, 2015 at 2:49 PM, Raul Kripalani  wrote:
>
> > Anton, fixed in ignite-1.5.
> >
> > You said "warnings" in plural, but I only found the one. Could you
> clarify
> > where else?
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Thu, Nov 19, 2015 at 9:37 AM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > wrote:
> >
> > > Raul,
> > >
> > > Of course I can,
> > > But this changes made by you recently, and it will be nice if you'll
> fix
> > > them.
> > >
> > > I've added some requirment to
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > Please see section Checklist before pust
> > > <
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Checklistbeforepust
> > > >
> > > .
> > >
> > > On Thu, Nov 19, 2015 at 12:06 PM, Raul Kripalani 
> > wrote:
> > >
> > > > Anton,
> > > >
> > > > Could you please just go ahead and fix it? This is a collaborative
> > > > project. Source is not owned by individual people.
> > > >
> > > > And let's not abuse the mailing list for details like this.
> > > >
> > > > Regards,
> > > > Raúl.
> > > > On 19 Nov 2015 08:49, "Anton Vinogradov" 
> > > wrote:
> > > >
> > > >> Hello,
> > > >>
> > > >> I've checked output of prerelease build of Ignite 1.5 and found
> > javadoc
> > > >> warnings like
> > > >> CamelStreamer.java:51: warning - Tag @link: malformed:
> > > >> "StreamMultipleTupleExtractor)"
> > > >>
> > > >> Raul, seems that was your changes. Could you please fix it?
> > > >>
> > > >
> > >
> >
>

Re: Ignite-1.5 Release

[Semyon Boikov]

Just merged single get optimizations (improvements in the last benchmarks
run: ~10% for atomic-put-get, ~5% for tx-put-get).

[jira] [Created] (IGNITE-1954) .Net: IIgnite.GetConfiguration

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1954:
---

 Summary: .Net: IIgnite.GetConfiguration
 Key: IGNITE-1954
 URL: https://issues.apache.org/jira/browse/IGNITE-1954
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: 1.5


Ability to obtain configuration of a running Ignite instance.
See Ignite.configuration() in Java.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)