Let's try your approach if you can embed it nicely into the site.
--
Denis
On Tue, Jun 26, 2018 at 3:55 PM Anton Vinogradov wrote:
> Anyway,
>
> I see 166 code contributors, event in case some persons have more than one
> account (like me) it definitely more that we have at contributors page.
>
Mo created IGNITE-8883:
--
Summary: Semaphore fails on network partitioning 2
Key: IGNITE-8883
URL: https://issues.apache.org/jira/browse/IGNITE-8883
Project: Ignite
Issue Type: Bug
Components:
Mo created IGNITE-8882:
--
Summary: Semaphore fails on network partitioning 1
Key: IGNITE-8882
URL: https://issues.apache.org/jira/browse/IGNITE-8882
Project: Ignite
Issue Type: Bug
Components:
Mo created IGNITE-8881:
--
Summary: Semaphore hangs on network partitioning
Key: IGNITE-8881
URL: https://issues.apache.org/jira/browse/IGNITE-8881
Project: Ignite
Issue Type: Bug
Components: da
Hello, Petr.
Thanks a lot!
I see success spring encryption tests now [1]
I've added encryption tests to core module also.
Can we set same rule for a core module?
[1]
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2290193573767653560&tab=testDetails
В Вт, 2
I’ve added JCE as it is described in documentation, but for some unknown reason
it won’t work on 1.8.0_u151.
So I’ve fix agent filter rule to run Spring build type only on 1.8.0_u171 (49
agents) and run it on all enabled compatible agents.
Looks like it fixed the issue.
> On 26 Jun 2018, at 19
Anyway,
I see 166 code contributors, event in case some persons have more than one
account (like me) it definitely more that we have at contributors page.
вт, 26 июн. 2018 г. в 19:55, Dmitry Pavlov :
> Hi Anton,
>
> IMO we can't limit contribution from community member only by contribution
> of
Hi,
This is a message that provides metrics for other nodes. You can take a look
at it in the source code.
However, looks like your client try to receive the acknowledgment for some
message from some node and there is no answer from this node. Possible that
the required node quit from the cluster
Hi Folks,
I hope you’re doing absolutely well.
Apache Ignite 2.6 (emergency release) code freezed with 14 following
changes (see below). Issues merged to master were migrated to 2.7 version,
same for not closed issues.
Please double check if there is any missed issue on the release page
https:
Amir Akhmedov created IGNITE-8880:
-
Summary: Add setIgnite() in SpringCacheManager and
SpringTransactionManager
Key: IGNITE-8880
URL: https://issues.apache.org/jira/browse/IGNITE-8880
Project: Ignite
I also think it will better to remove setDataMap support cause
1. It's making extra pressure on GC by keeping entries on heap
2. It has difficult logic to support with lots of nuances
3. To maintain setDataMap today GridCacheMapEntry calls
cctx.dataStructures().onEntryUpdated() on each entry mutati
+1 to Dmitriy's stance.
IGNITE-6055 doesn't look like something that needs to halt this release.
Plus, let me remind us that it's an emergency release that has to solve
severe problems at the persistence layer. What planned to be released
within 2 weeks got stuck for almost a month.
Dmitriy, as a
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4254
---
Hello Igniters,
I planing to start work on IGNITE-5427 and I little confused.
The Baseline Topology documentation (
https://apacheignite.readme.io/docs/baseline-topology#section-setting-the-topology-from-code)
says that method IgniteCluster.setBaseLineTopogy() should automatically
activate the clu
Hi Anton,
IMO we can't limit contribution from community member only by contribution
of code (it may be wiki, documenation, examples, popularization of Ignite,
etc, - literally any contribution), so it is more general way to maintain
contributors list as is.
Sincerely,
вт, 26 июн. 2018 г. в 15:2
Hi Nikolay,
why this ticket should be included into emergency release?
I agree in case
1) Vladimir has time to review it now,
2) we have clear motivation why it is emergency change.
We are still going to do 2.7 release as normal Ignite release later.
Sincerely,
Dmitriy Pavlov
вт, 26 июн. 2018
Also, Igniters, be aware
https://issues.apache.org/jira/browse/IGNITE-8534 merged to master and cherry
picked to 2.6 branch.
В Вт, 26/06/2018 в 19:29 +0300, Nikolay Izhikov пишет:
> Hello, Igniters.
>
> We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
>
> IGNITE-6055 has to b
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/4262
IGNITE-8863 Tx rollback can cause remote tx hang.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8863
Alte
I will try to make it tomorrow.
> On 26 Jun 2018, at 19:27, Nikolay Izhikov wrote:
>
> Petr, can you make suggested jdk upgrade?
>
> В Пн, 25/06/2018 в 14:28 +0300, Nikolay Izhikov пишет:
>> Petr.
>>
>> One more thing:
>>
>> We need to install "Java Cryptography Extension (JCE) Unlimited St
Hello, Igniters.
We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
IGNITE-6055 has to be included in 2.6, also.
Final review from Vladimir required to merge this ticket.
Do we have a chance to include this ticket to 2.6?
В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> Hi
Petr, can you make suggested jdk upgrade?
В Пн, 25/06/2018 в 14:28 +0300, Nikolay Izhikov пишет:
> Petr.
>
> One more thing:
>
> We need to install "Java Cryptography Extension (JCE) Unlimited Strength
> Jurisdiction Policy Files" [1] to enable usage of JDK provided crypto
> algorithmes.
> Oth
Hi Igniters,
I've prepared wiki page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
started to reassign existing issues to 2.7.
Sincerely,
Dmitriy Pavlov
сб, 23 июн. 2018 г. в 2:58, Denis Magda :
> Thanks folks!
>
> Dmitriy P., please proceed with the release finalizat
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/4261
Ignite 2.5.1 p8 TC check
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p8
Alternatively you can rev
Dmitry Sherstobitov created IGNITE-8879:
---
Summary: Blinking baseline node sometimes unable to connect to
cluster
Key: IGNITE-8879
URL: https://issues.apache.org/jira/browse/IGNITE-8879
Project:
Andrew Mashenkov created IGNITE-8878:
Summary: Make WebConsole agent logging more verbose.
Key: IGNITE-8878
URL: https://issues.apache.org/jira/browse/IGNITE-8878
Project: Ignite
Issue Ty
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4260
IGNITE-8869: Explicitly fail hanging test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ivandasch/ignite ignite-8869
Alternatively you ca
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4259
IGNITE-8877
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8877
Alternatively you can review and apply these c
Ilya Lantukh created IGNITE-8877:
Summary:
PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation leads
to OutOfMemoryError
Key: IGNITE-8877
URL: https://issues.apache.org/jira/browse/IGNITE-8
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1709
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4033
---
Alexei Scherbakov created IGNITE-8876:
-
Summary: Deactivate before checkpoint may lead to assertion and
node failture.
Key: IGNITE-8876
URL: https://issues.apache.org/jira/browse/IGNITE-8876
Proje
Andrew Mashenkov created IGNITE-8875:
Summary: Add JMX methods to block\unblock new incoming connections
from thin clients.
Key: IGNITE-8875
URL: https://issues.apache.org/jira/browse/IGNITE-8875
It is already set to test.
> On 26 Jun 2018, at 15:26, Nikolay Izhikov wrote:
>
> For `RDD` suite, we need use `test` goal instead of `surefire:test`, also.
>
> Because, scala tests runs with org.scalatest:scalatest-maven-plugin:2.0.0
>
>
> В Вт, 26/06/2018 в 14:53 +0300, Nikolay Izhikov пиш
Github user antkr closed the pull request at:
https://github.com/apache/ignite/pull/4245
---
Why should I?
It is project wide configuration (used in all build in project) and scala-2.10
still exists in root pom.xml
This profile only adds some modules to reactor and does not effect any other
configuration.
> On 26 Jun 2018, at 14:53, Nikolay Izhikov wrote:
>
> Please, remove `scala-
For `RDD` suite, we need use `test` goal instead of `surefire:test`, also.
Because, scala tests runs with org.scalatest:scalatest-maven-plugin:2.0.0
В Вт, 26/06/2018 в 14:53 +0300, Nikolay Izhikov пишет:
> Please, remove `scala-2.10` from profiles, also.
>
> В Вт, 26/06/2018 в 14:39 +0300, Petr
Why we cant just use this page?
https://github.com/apache/ignite/graphs/contributors
вт, 26 июн. 2018 г. в 15:20, Denis Magda :
> Only static code is allowed on the site. The downloads' code snippets are
> prepared and enabled by INFRA.
>
> --
> Denis
>
> On Tue, Jun 26, 2018 at 5:18 AM Anton Vin
Only static code is allowed on the site. The downloads' code snippets are
prepared and enabled by INFRA.
--
Denis
On Tue, Jun 26, 2018 at 5:18 AM Anton Vinogradov wrote:
> Can we generate contributors page automatically?
> Git history tells me we missed more than one contributor :)
>
> вт, 26 и
Have no idea how extra /tr> tag popped up. The history of recent changes is
clean. Not obvious how to fix it.
Prachi, could look into this?
--
Denis
On Tue, Jun 26, 2018 at 2:11 AM Anton Vinogradov wrote:
> Denis, could you please also fix Committers table?
> Seems it was broken on last append
Can we generate contributors page automatically?
Git history tells me we missed more than one contributor :)
вт, 26 июн. 2018 г. в 15:14, Pavel Kovalenko :
> Igniters,
>
> I've just noticed that I also not mentioned in Contributors table.
>
> вт, 26 июн. 2018 г. в 12:11, Anton Vinogradov :
>
> >
Igniters,
I've just noticed that I also not mentioned in Contributors table.
вт, 26 июн. 2018 г. в 12:11, Anton Vinogradov :
> Denis, could you please also fix Committers table?
> Seems it was broken on last append.
>
> пн, 25 июн. 2018 г. в 22:18, Denis Magda :
>
> > Done, thanks for your contr
Denis,
I think that better case is to remove onheap optimisation/duplication.
This brings no drop to frequently used operations (put/remove), but even
will make it slightly faster.
The only one question we have here is "is it possible to restore onheap map
in easy way?".
Seems that answer is no,
I see ok thanks!
On Tue, Jun 26, 2018 at 12:18 PM, Dmitriy Setrakyan
wrote:
>
>
> On Tue, Jun 26, 2018 at 9:58 AM, Evaldas Miliauskas <
> e.miliaus...@stacktome.com> wrote:
>
>> I see, could you give an example about "changing arg name manually"? Or
>> do you mean only constant values can be pas
I see, could you give an example about "changing arg name manually"? Or do
you mean only constant values can be passed as args in that case?
On Tue, Jun 26, 2018 at 11:28 AM, Dmitriy Setrakyan
wrote:
>
>
> On Tue, Jun 26, 2018 at 9:23 AM, Evaldas Miliauskas <
> e.miliaus...@stacktome.com> wrote:
Anton,
Will it be possible to reuse such a functionality for the rest of data
structures? I would invest our time in this if all data structures would be
able to work with Ignite persistence this way.
--
Denis
On Tue, Jun 26, 2018 at 1:53 AM Anton Vinogradov wrote:
> >> Why don't we read data
Hey, I was trying to test queries that use condition "? is null" to be able
to use explain command and see what query plan is generated.
On Tue, Jun 26, 2018 at 11:15 AM, Dmitriy Setrakyan
wrote:
> Hi Evaldas,
>
> I am not sure why do you need to pass the "?" from the Web Console? Why
> not just
Please, remove `scala-2.10` from profiles, also.
В Вт, 26/06/2018 в 14:39 +0300, Petr Ivanov пишет:
> I’ve modified list of suites and added ‘scala’ and ’scala-test’ to profiles
> list.
> Please check build.
>
>
>
> > On 26 Jun 2018, at 14:28, Nikolay Izhikov wrote:
> >
> > Petr.
> >
> > 1.
Guys,
We have auto-activation on restart of persistent cluster when last
baseline node joins the cluster. On first start we have no baseline
topology, and thus no auto-activation.
I think it would be useful to add java snippet to Ignite documentation
that will safely activate the cluster on
I’ve modified list of suites and added ‘scala’ and ’scala-test’ to profiles
list.
Please check build.
> On 26 Jun 2018, at 14:28, Nikolay Izhikov wrote:
>
> Petr.
>
> 1. We need *only* TEST_SUITE = "IgniteRDDTestSuite,IgniteDataFrameSuite"
> other Specs included in this two.
>
> 2. `scala-
Vladimir,
Auto-activation on the first start?
Please, shared an issue link if you have.
On Tue, Jun 26, 2018 at 11:29 AM Vladimir Ozerov
wrote:
> Pavel,
>
> As far as I know we agreed to implement auto activation in one of the
> nearest releases. Am I missing something?
>
> вт, 26 июня 2018 г.
Petr.
1. We need *only* TEST_SUITE = "IgniteRDDTestSuite,IgniteDataFrameSuite" other
Specs included in this two.
2. `scala-2.10` has to be removed.
3. We need both `scala` and `scala-test` profile.
В Вт, 26/06/2018 в 14:10 +0300, Petr Ivanov пишет:
> I did not understand how should I reconfi
I did not understand how should I reconfigure RDD build configuration.
1. TEST_SUITE currently has value of
'IgniteRDDTestSuite,AbstractDataFrameSpec,Entity,EntityTestAllTypeFields,IgniteCatalogSpec,IgniteDataFrameSchemaSpec,IgniteDataFrameSuite,IgniteDataFrameWrongConfigSpec,IgniteRDDSpec,Ignite
Dmitry Sherstobitov created IGNITE-8874:
---
Summary: Blinking node in cluster may cause data corruption
Key: IGNITE-8874
URL: https://issues.apache.org/jira/browse/IGNITE-8874
Project: Ignite
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4258
IGNITE-8857 HashMap is returned instead of filtering wrapper
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/4257
IGNITE-7967 DataRegionMetrics#totalAllocatedPages is invalid if metriâ¦
â¦cs were enabled at runtime
You can merge this pull request into a Git repository by running:
$ git pull https://gi
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4227
---
On Tue, Jun 26, 2018 at 9:58 AM, Evaldas Miliauskas <
e.miliaus...@stacktome.com> wrote:
> I see, could you give an example about "changing arg name manually"? Or do
> you mean only constant values can be passed as args in that case?
>
What I meant is passing an actual value instead of the "?".
Denis, could you please also fix Committers table?
Seems it was broken on last append.
пн, 25 июн. 2018 г. в 22:18, Denis Magda :
> Done, thanks for your contributions!
>
> --
> Denis
>
> On Mon, Jun 25, 2018 at 6:13 AM Иван Федоров wrote:
>
> > Hi, Igniters!
> > I'm contributor and I'm not ment
>> Why don't we read data straight from the persistence layer warming RAM up
>> in the background?
Because it's not a trivial task to finish such loading on unstable
topology.
That's possible, ofcourse, but solution and complexity will be almost
equals to WAL enable/disable.
пн, 25 июн. 2018 г. в
Pavel,
As far as I know we agreed to implement auto activation in one of the
nearest releases. Am I missing something?
вт, 26 июня 2018 г. в 0:56, Pavel Kovalenko :
> Igniters,
>
> By the results of the recent Ignite meeting at St. Petersburg I've noticed
> that some of our users getting stuck w
On Tue, Jun 26, 2018 at 9:23 AM, Evaldas Miliauskas <
e.miliaus...@stacktome.com> wrote:
> Hey, I was trying to test queries that use condition "? is null" to be
> able to use explain command and see what query plan is generated.
>
Got it. Currently web console accepts SQL statements, not JDBC st
Hi Evaldas,
I am not sure why do you need to pass the "?" from the Web Console? Why not
just pass the real parameter?
D.
On Mon, Jun 25, 2018 at 7:05 PM, Evaldas Miliauskas <
e.miliaus...@stacktome.com> wrote:
> Right now I cannot execute a following query in Web Console:
> "select count(*) fro
62 matches
Mail list logo
