Hi Sudhanshu,
Welcome to the Ignite community!
You can find all the project-related resources here:
https://ignite.apache.org/community/resources.html
Additionally, you should take a look at the instructions on how to
contribute here:
https://ignite.apache.org/community/contribute.html
Some ins
Pavel Konstantinov created IGNITE-1385:
--
Summary: Confused warning about portable marshaller
Key: IGNITE-1385
URL: https://issues.apache.org/jira/browse/IGNITE-1385
Project: Ignite
Issue
Ticket filed:
https://issues.apache.org/jira/browse/INFRA-10272
D.
On Thu, Sep 3, 2015 at 4:03 PM, Konstantin Boudnik wrote:
> I believe an INFRA ticket needs to be filed for this.
>
> On Thu, Sep 03, 2015 at 01:36PM, Raul Kripalani wrote:
> > Hey guys,
> >
> > Not sure if you're aware and alre
On Mon, Sep 7, 2015 at 6:05 PM, Andrey Kornev
wrote:
> Hello,
>
> I'd like to be able to deploy my cluster-wide singleton services all
> collocated on the same cluster node. What is the best way to achieve that?
>
> Ideally, I'd like to be able to define the "service groups" where all
> services
Hello,
I'd like to be able to deploy my cluster-wide singleton services all collocated
on the same cluster node. What is the best way to achieve that?
Ideally, I'd like to be able to define the "service groups" where all services
in a group would be deployed on the same node, whereas the differ
Sergey Sidorov created IGNITE-1384:
--
Summary: Compute job ids duplication
Key: IGNITE-1384
URL: https://issues.apache.org/jira/browse/IGNITE-1384
Project: Ignite
Issue Type: Bug
That's what we do in Bigtop, cause otherwise there's no way of building the
stack on top of Hadoop 2.6.0
On Mon, Sep 07, 2015 at 10:09AM, Dmitriy Setrakyan wrote:
> On Mon, Sep 7, 2015 at 6:24 AM, Nikolay Tikhonov
> wrote:
>
> > >
> > > I think the same question stands - what is the main chall
On Mon, Sep 7, 2015 at 6:24 AM, Nikolay Tikhonov
wrote:
> >
> > I think the same question stands - what is the main challenge here?
>
> Yarn module is compatible with Hadoop version 2.7.0 and above. Exist two
> way: set different variables for yarn and hadoop modules or make yarn
> module compile
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/73
Migrate JDBC driver from Java client to Ignite node in client mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-12
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/29
---
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 enable
Too complex and confusing. Just open next version eg 1.5 and move tickets that
won't be fixed in 1.4 to the next one (effectively your pending )
On September 7, 2015 6:16:15 AM PDT, Yakov Zhdanov wrote:
>I would introduce new version "pending". This way we can distinguish
>newly
>filed tickets (
On Mon, Sep 7, 2015 at 6:16 AM, Yakov Zhdanov wrote:
> I would introduce new version "pending". This way we can distinguish newly
> filed tickets (version default), postponed tickets (pending) and scheduled
> ones (e.g. 1.4)
>
I really don't see what version "pending" would accomplish. Might as
Artem Shutak created IGNITE-1383:
Summary: Need to have ability to use apply-pull-request.sh script
for non-master branches
Key: IGNITE-1383
URL: https://issues.apache.org/jira/browse/IGNITE-1383
Proj
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/72
10724 .Net: Improve compatibility tests coverage.
Fake pull request for TC. Please ignore.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupi
We could use the brief explanation:
*if build fails due known issue IGNITE-1195 please remove yarn module from
root pom.xml or exclude via -pl !/modules/yarn (for maven version >= 3.2.1)*
On Mon, Sep 7, 2015 at 4:24 PM, Nikolay Tikhonov
wrote:
> >
> > I think the same question stands - what is
>
> I think the same question stands - what is the main challenge here?
Yarn module is compatible with Hadoop version 2.7.0 and above. Exist two
way: set different variables for yarn and hadoop modules or make yarn
module compiled with older hadoop versions.
Sounds good
On Mon, Sep 7, 2015 at 4:16 PM, Yakov Zhdanov wrote:
> I would introduce new version "pending". This way we can distinguish newly
> filed tickets (version default), postponed tickets (pending) and scheduled
> ones (e.g. 1.4)
>
> Thoughts?
>
> Thanks!
>
> Yakov
> On Sep 7, 2015 15:31,
I would introduce new version "pending". This way we can distinguish newly
filed tickets (version default), postponed tickets (pending) and scheduled
ones (e.g. 1.4)
Thoughts?
Thanks!
Yakov
On Sep 7, 2015 15:31, "Anton Vinogradov" wrote:
> Seems worth specify "None" fixversion instead of 1.5.
Vladimir Ozerov created IGNITE-1382:
---
Summary: Consider using "JavaCritical_" prefix to speedup short
Java -> platform callbacks.
Key: IGNITE-1382
URL: https://issues.apache.org/jira/browse/IGNITE-1382
I'm ok
On Mon, Sep 7, 2015 at 3:31 PM, Anton Vinogradov
wrote:
> Seems worth specify "None" fixversion instead of 1.5.
> Thoughts?
>
> On Mon, Sep 7, 2015 at 2:50 PM, Sergey Kozlov
> wrote:
>
> > Guys
> >
> > We still have unclosed/unresolved more than 100 issues.
> > Could you review issues as
Seems worth specify "None" fixversion instead of 1.5.
Thoughts?
On Mon, Sep 7, 2015 at 2:50 PM, Sergey Kozlov wrote:
> Guys
>
> We still have unclosed/unresolved more than 100 issues.
> Could you review issues assigned on you and move then on next release (1.5)
> if it won't be done for 1.4?
>
>
Pavel Tupitsyn created IGNITE-1381:
---
Summary: Incorrect marshalling and/or unmarshalling of
unregistered types
Key: IGNITE-1381
URL: https://issues.apache.org/jira/browse/IGNITE-1381
Project: Ignit
Guys
We still have unclosed/unresolved more than 100 issues.
Could you review issues assigned on you and move then on next release (1.5)
if it won't be done for 1.4?
Thanks!
On Fri, Sep 4, 2015 at 3:24 PM, Vladimir Ozerov
wrote:
> Please disregard p.2 and p.3 as they are out of Ignite scope.
>
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/71
Fix GridUpdateNotifier stopping on Ignite stopping
Fix GridUpdateNotifier stopping on Ignite stopping. PR to ignite-1.4
You can merge this pull request into a Git repository by running:
$ git
Github user ashutakGG closed the pull request at:
https://github.com/apache/ignite/pull/53
---
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 en
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/70
IGNITE-1367 Platforms .Net: Move grid executable to Ignite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1367
Altern
Pavel Konstantinov created IGNITE-1380:
--
Summary: Random eviction policy for near cache works incorrectly
Key: IGNITE-1380
URL: https://issues.apache.org/jira/browse/IGNITE-1380
Project: Ignite
Hello Developers,
I am Sudhanshu Gupta, software engineer working in Bangalore, India.
I am willing to contribute to the project. I have forked and cloned the
repo in my local. I want to get start on it. It would be great if anyone
from the community can help to understand the codebase and let me
28 matches
Mail list logo
