Pavel,
Can you give a cue where can be uploaded Nuget packages found?
On Mon, 16 Jul 2018 at 23:37, Pavel Tupitsyn wrote:
> Petr,
>
> This is the same build that I have linked. Is there anything I should pay
> attention to?
>
> On Mon, Jul 16, 2018 at 11:05 PM Petr Ivanov wrote:
>
> > Pavel,
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4370
Ignite 2.4.7.b5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.7.b5
Alternatively you can review and
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose
Released 2.6 readme.io documentation.
Andrey, I'll send you an announcement template privately. This time there
is no sense to publish a blog post for me, so you can announce the release
once all the post-steps are completed.
--
Denis
On Mon, Jul 16, 2018 at 1:37 PM Pavel Tupitsyn wrote:
>
On Mon, Jul 16, 2018 at 5:42 PM, Yakov Zhdanov wrote:
> Dmitry, let's have only getNext() same as jdbc. All other shortcuts seem to
> overload API without adding much value.
>
Agree. Do you mind creating a ticket?
Petr,
This is the same build that I have linked. Is there anything I should pay
attention to?
On Mon, Jul 16, 2018 at 11:05 PM Petr Ivanov wrote:
> Pavel,
>
>
> Before uploading, please check this [1] build.
>
>
> [1]
>
Pavel,
Before uploading, please check this [1] build.
[1]
https://ci.ignite.apache.org/viewLog.html?buildId=1502954=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages=buildLog&_focus=230#_state=230
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4369
Ignite-9013
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9013
Alternatively you can review and apply these
Dmitry, it hink we can do this change right away. All we need is to add
proper error message on cache config validation in order to tell user that
default changed and manual configuration is needed for compatibility.
--Yakov
2018-07-16 15:47 GMT+03:00 Dmitry Karachentsev :
> Created a ticket
Sure, I will do. Sign up to JIRA and wiki, it is open for everyone. Then I
need username(s) to add appropriate contributor role.
пн, 16 июл. 2018 г. в 20:53, Yakov Zhdanov :
> I think you need to signup to Apache jira and let us know your user ID so
> we can add you to contributors. Dmitry
Maxim, I looked at the code you provided. I think we need to add some
timeout validation and output warning to logs on demander side in case
there is no supply message within 30 secs and repeat demanding process.
This should apply to any demand message throughout the rebalancing process
not only
Eduard Shangareev created IGNITE-9013:
-
Summary: Node stop hangs if there was cache activities in Service
Processor
Key: IGNITE-9013
URL: https://issues.apache.org/jira/browse/IGNITE-9013
I think you need to signup to Apache jira and let us know your user ID so
we can add you to contributors. Dmitry Pavlov, can you please help.
--Yakov
2018-07-12 18:54 GMT+03:00 vgrigorev :
> Hi colleges!
>
> I would like move topic to suitable place.
>
> Please only clarify how to do it:
> In a
Ignite site is updated. Most artifacts are published.
Waiting for publishing of Docker images and 2.6 related docs. Also it
would be great to check NuGet packages.
On Mon, Jul 16, 2018 at 7:32 PM Denis Magda wrote:
>
> Andrey,
>
> I'll publish the docs later today.
>
> --
> Denis
>
> On Mon, Jul
Igniters, may be I'm wrong, but in my opinion it slightly different
functionality.
Lifecycle is more like user functionality witch provide simple way to add
additional behavior to cluster.
I can implement interface LifecycleBean, do some logic (may be inject
Ignite instance into it),
add my
Oops, wrong link.
The correct one:
http://apache-ignite-users.70518.x6.nabble.com/Thin-client-doesn-t-support-Expiry-Policies-tt22422.html
From: Stanislav Lukyanov
Sent: 16 июля 2018 г. 14:18
To: dev@ignite.apache.org
Subject: RE: Can .NET thin client have cache expire policy?
The same question
Andrey,
I'll publish the docs later today.
--
Denis
On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura wrote:
> Dmitry,
>
> I'm updating the site at this moment. Could somebody publish 2.6
> documentation on readme.io site?
> On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan
> wrote:
> >
> > Is
Pavel,
could you please assist with NuGet packages?
On Mon, Jul 16, 2018 at 6:46 PM Andrey Gura wrote:
>
> Dmitry,
>
> I'm updating the site at this moment. Could somebody publish 2.6
> documentation on readme.io site?
> On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan
> wrote:
> >
> > Is
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4368
IGNITE-7165 Rebalance control version holds by exchange thread
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite av-ignit-7165-2
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4109
---
Dmitriy,
Yes, this achieves the same purpose, thanks for hint.
Updated PR to use strictly setRollbackOnly().
ср, 11 июл. 2018 г. в 4:17, Dmitriy Setrakyan :
> Anton,
>
> Committing or rolling back from MXBean is OK, because it is not a listener,
> but a direct invocation. However, it is not OK
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1558
---
Dmitry,
I'm updating the site at this moment. Could somebody publish 2.6
documentation on readme.io site?
On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan wrote:
>
> Is there a reason why 2.6 has not been uploaded to the website yet?
>
> D.
>
> On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura
I checked the source code and found that this issue may be caused by this
line
org.apache.ignite.internal.processors.cache.GridCacheProcessor #1452
CacheEvictionManager evictMgr = (nearEnabled || cfg.isOnheapCacheEnabled())
? new GridCacheEvictionManager() : new CacheOffheapEvictionManager();
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4217
---
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4367
IGNITE-9012 Test IgniteServiceReassignmentTest.testZombieAssignmentsCâ¦
â¦leanup fails
Signed-off-by: EdShangGG
You can merge this pull request into a Git repository by running:
Dmitry, let's have only getNext() same as jdbc. All other shortcuts seem to
overload API without adding much value.
--Yakov
2018-07-16 17:33 GMT+03:00 Dmitriy Setrakyan :
> Well, instead of getFirst(), I would have getNext(). This way we do not
> have to keep the first entry forever, which
Is there a reason why 2.6 has not been uploaded to the website yet?
D.
On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura wrote:
> Igniters,
>
> Apache Ignite 2.6.0 release (RC1) has been accepted.
>
> 5 "+1" binding votes received:
>
> - Alexey Goncharuk
> - Alexey Kuznetsov
> - Andrey Gura
> -
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4357
---
Well, instead of getFirst(), I would have getNext(). This way we do not
have to keep the first entry forever, which could present a problem in case
if entry is too large.
As far as initializing keepAll() to false - completely agree.
D.
On Mon, Jul 16, 2018 at 4:43 PM, Alexey Goncharuk <
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4256
---
No objections from my side. Would be nice to receive some feedback from
other community members, though, because this is formally a breaking change.
пн, 16 июл. 2018 г. в 16:40, Yakov Zhdanov :
> Guys, it seems we need to deprecate getAll() and remove it in 3.0. I think
> it is usable only for
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4366
alternative fix for client reconnect with ZookeeperDiscoverySpi
You can merge this pull request into a Git repository by running:
$ git pull
Guys, it seems we need to deprecate getAll() and remove it in 3.0. I think
it is usable only for queries that return 1 row. Every other case needs
iteration. So having getFirst() seems to be better. Thoughts?
As far as ScanQuery I think we can properly initialize keepAll to false on
scan query
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4243
---
Hi,
You can edit the ticket so it does not display any information, but the
content will be still accessible in the history. We can change the ticket
visibility to private, but it will be still be accessible for committers. I
suggest you contact Apache infra team regarding your request.
ср, 20
Eduard Shangareev created IGNITE-9012:
-
Summary: Test
IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails
Key: IGNITE-9012
URL: https://issues.apache.org/jira/browse/IGNITE-9012
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4365
IGNITE-8985 - Node segmented itself after connRecoveryTimeout. Improvâ¦
â¦ed loopback resolving from IGNITE-8683.
You can merge this pull request into a Git repository by running:
$
Peter Ivanov created IGNITE-9010:
Summary: Move web-console build to dedicated root directory
Key: IGNITE-9010
URL: https://issues.apache.org/jira/browse/IGNITE-9010
Project: Ignite
Issue
Igor Sapego created IGNITE-9008:
---
Summary: CPP Thin: Implement benchmark for C++ thin
Key: IGNITE-9008
URL: https://issues.apache.org/jira/browse/IGNITE-9008
Project: Ignite
Issue Type: New
The same question is being discussed on the user-list:
https://stackoverflow.com/questions/51314852/is-there-a-workaround-to-use-thin-client-with-cache-expiry-policy-in-apache-igni
Stan
From: Dmitriy Setrakyan
Sent: 16 июля 2018 г. 3:03
To: dev
Cc: Pavel Tupitsyn
Subject: Can .NET thin client
GitHub user anton-vinogradov opened a pull request:
https://github.com/apache/ignite/pull/4364
IGNITE-8783
Signed-off-by: Anton Vinogradov
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-8783
Alternatively
Roman Guseinov created IGNITE-9007:
--
Summary: cache.invoke() fails because of
UnregisteredClassException
Key: IGNITE-9007
URL: https://issues.apache.org/jira/browse/IGNITE-9007
Project: Ignite
Hello!
Can we also bypass WAL for such mode automatically?
However, we will definitely need a 'normal' mode of DataStreamer operation,
for people who use dataStreamer with custom stream transformers on existing
data in use.
Regards,
--
Ilya Kasnacheev
2018-07-14 12:33 GMT+03:00 Vladimir
Alexey Goncharuk created IGNITE-9006:
Summary: Add per-call tracing capabilities for IgniteCache#{get,
getAll} methods
Key: IGNITE-9006
URL: https://issues.apache.org/jira/browse/IGNITE-9006
45 matches
Mail list logo
