Hello Ignite community,
I'd like to do an enhancement on Ignite, my JIRA id is ldzhjn.
Please grant permissions.
Thanks
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/4020
IGNITE-8525: Support for IgniteZeroMqStreamer non-multi-part pub-sub.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite IGNITE-852
Roman Shtykh created IGNITE-8525:
Summary: Support for IgniteZeroMqStreamer non-multi-part pub-sub
Key: IGNITE-8525
URL: https://issues.apache.org/jira/browse/IGNITE-8525
Project: Ignite
Issu
Denis Magda created IGNITE-8524:
---
Summary: Document consistency check utilities
Key: IGNITE-8524
URL: https://issues.apache.org/jira/browse/IGNITE-8524
Project: Ignite
Issue Type: Task
Igniters,
With the help of Stanislav Lukyanov and Ivan Rakov, we could make our
baseline topology documentation much better and vivid. Check up the new
sections that did a better job explaining the topology, cover common usage
scenarious and explain how to trigger the rebalancing programmatically
That's a good point.
Taras, Vladimir, as those who contributed the authentication could you
schedule this improvement for future releases?
Oleksandr, as for now, please use your own version of the script. Moreover,
you can update the existing scripts and ask the community to accept your
changes t
Hi,
This guy had made last commit in https://github.com/apacheignite repo Nov
2017:
https://github.com/TikhonovNikolay?tab=repositories
May be hi is from GridGane...
Thanks,
Aleksandr
On 17 May 2018 at 21:27, Vyacheslav Daradur wrote:
> Hi, there is such GitHub profile:
> https://github.com/a
Hi, there is such GitHub profile:
https://github.com/apacheignite
But I don't know who manage that.
On Thu, May 17, 2018 at 9:22 PM, Aleksandr Sokolovskii
wrote:
> Hi Igor,
>
> Of course I am ready to donate code.
>
> You have to know that GitHub is source code repo and package repo for build
>
Hi Igor,
Of course I am ready to donate code.
You have to know that GitHub is source code repo and package repo for build
for Go lang.
I see that .NET client is deep inside Apache Ignite source code structure.
It's not very comfortable for Go lang developers.
It's best practice when each Go lang
Hi,
Would IGNITE-6827 potentially be a workaround for IGNITE-6967? I understand
that eventually IGNITE-6967 will not be applicable once the service grid
stops using the utility cache and switches to discovery messages, but I've
encountered odd deadlocks with PME and I'm growing more suspicious tha
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4018
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3651
---
Alexey,
Makes sense to merge.
--
Denis
On Thu, May 17, 2018 at 8:53 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Denis,
>
> The issue with page corruption may manifest itself when a node is stopped
> during partition eviction (basically, a random chance on topology change
> scena
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4019
IGNITE-8405 Backport to 2.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13827
Alternatively you can review
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/4018
IGNITE-8423 Control utility may block when joining node is watiting fâ¦
â¦or partition map exchange.
You can merge this pull request into a Git repository by running:
$ git pull https:/
Hi Nikolay
Could you take a look in [1] as author of spark examples? Looks like the
structure is broken.
[1] https://issues.apache.org/jira/browse/IGNITE-8523
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Denis,
The issue with page corruption may manifest itself when a node is stopped
during partition eviction (basically, a random chance on topology change
scenario).
The issue with WAL iterator can manifest during historical rebalancing
(this is less likely than the previous issue).
2018-05-17 18
Sergey Kozlov created IGNITE-8523:
-
Summary: Java and Scala spark examples are mixed
Key: IGNITE-8523
URL: https://issues.apache.org/jira/browse/IGNITE-8523
Project: Ignite
Issue Type: Bug
Alexey Kuznetsov created IGNITE-8522:
Summary: Transaction incorrect state after cache closed
Key: IGNITE-8522
URL: https://issues.apache.org/jira/browse/IGNITE-8522
Project: Ignite
Issue
We keep facing the issues that postpone the release over and over again
which seems like a never-ending story.
What are the changes the users come across the 2 latest bugs you've
mentioned (any special conditions)?
What's the overall state of our testing cycles? When would we send the
release for
Another issue that may lead to incorrect recovery on node startup is
https://issues.apache.org/jira/browse/IGNITE-8464 which is already in PA. I
suggest we also include it to 2.5 given that fix improves stability of the
persistence layer. Any objections?
2018-05-17 16:55 GMT+03:00 Ivan Rakov :
>
Sergey Kozlov created IGNITE-8521:
-
Summary: CacheContinuousQueryWithTransformerExample fails with NPE
Key: IGNITE-8521
URL: https://issues.apache.org/jira/browse/IGNITE-8521
Project: Ignite
By the way, Alexandr,
Do you want to donate your client to Apache Ignite, so we
are going to include it in our release, or would you prefer
keep it separate?
Best Regards,
Igor
On Thu, May 10, 2018 at 1:09 PM, Igor Sapego wrote:
> Aleksandr,
> I'm currently working on the improvement of the d
GitHub user a-polyakov reopened a pull request:
https://github.com/apache/ignite/pull/3921
IGNITE-7883 add check property "key configuration" in cache configuration
â¦tions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/a-polyak
Github user a-polyakov closed the pull request at:
https://github.com/apache/ignite/pull/3921
---
Andrey, Igniters,
I bumped into this issue while trying to reproduce another:
https://issues.apache.org/jira/browse/IGNITE-8320
I think, this fix worth being cherry-picked into 2.5. Possibility of
AssertionError on persistence level is really undesirable for Ignite as
a product.
Best Regards
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4017
IGNITE-8461 Scala-2.10 modules compilation failure under JDK 9
* fixed Scala 2.10 compilation on JDK9
* updated other Scala versions
You can merge this pull request into a Git repository by r
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4016
IGNITE-8320 Backport to 2.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13826
Alternatively you can review
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/3584
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3991
---
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4015
Ignite 6587
For test purposes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6587
Alternatively you c
GitHub user kotamrajuyashasvi opened a pull request:
https://github.com/apache/ignite/pull/4014
IGNITE-6500
POJO fields of java wrapper type are not retaining null values from
Cassandra persistent store, while using ignite's CassandraCacheStoreFactory.
You can merge this pull reque
Github user kotamrajuyashasvi closed the pull request at:
https://github.com/apache/ignite/pull/2992
---
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4013
IGNITE-8520 ignite-gce/ignite-shmem is redundant
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8520
Alternativ
Sergey Kozlov created IGNITE-8520:
-
Summary: ignite-gce/ignite-shmem
Key: IGNITE-8520
URL: https://issues.apache.org/jira/browse/IGNITE-8520
Project: Ignite
Issue Type: Bug
Affects Versio
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4012
IGNITE-8516 checked not null constraint
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite ignite-8516
Alternatively you can review
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3990
---
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4011
Ignite-2.4.5-p1
For test purposes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.5-p1
Alternatively you c
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3985
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4002
---
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/2962
---
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/3967
---
Alexey Kuznetsov created IGNITE-8519:
Summary: Web Console: Refactor to from Font Awesome to svg icons
"Change token" panel on Profile screen
Key: IGNITE-8519
URL: https://issues.apache.org/jira/browse/IGNITE-
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/4010
IGNITE-8491
Add JMX flag: Is the node in baseline or not?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8491
44 matches
Mail list logo