Peter Ivanov created IGNITE-8316:
Summary: Update RPM and DEB documentation
Key: IGNITE-8316
URL: https://issues.apache.org/jira/browse/IGNITE-8316
Project: Ignite
Issue Type: Task
Dmitriy Shabalin created IGNITE-8317:
Summary: Loader bug in safari
Key: IGNITE-8317
URL: https://issues.apache.org/jira/browse/IGNITE-8317
Project: Ignite
Issue Type: Bug
Compo
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/3872
IGNITE-8315 Print info about partition distribution to log
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-8315
Alte
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/3867
---
Roman Kondakov created IGNITE-8318:
--
Summary: MVCC TX: Scan query call throws an exception when it is
mixed with Key-Value API in the same transaction.
Key: IGNITE-8318
URL: https://issues.apache.org/jira/browse
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/3873
IGNITE-5979
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite ignite-5979
Alternatively you can review and apply these changes as t
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/3874
IGNITE-7319: Cancelable future task for backup cleaner should be closed on
CacheContinuousQueryManager stop
When cache is created then new CONTINUOUS_QUERY task is created too. This
task sho
Oleg Ostanin created IGNITE-8319:
Summary: Examples do not launch from Intellij Idea because ML
module is configured incorrectly.
Key: IGNITE-8319
URL: https://issues.apache.org/jira/browse/IGNITE-8319
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/3875
IGNITE-8190 Print out an information message when local node is not in
baseline
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-pl
Vyacheslav Koptilin created IGNITE-8320:
---
Summary: Page corruption during the rebalancing cache.
Key: IGNITE-8320
URL: https://issues.apache.org/jira/browse/IGNITE-8320
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2878
---
They can be executed locally, and no, you don't need any library.
It is just that Teamcity plugin depends on exact version of Boost,
as I mentioned before. You can disable it if you are going to run
tests locally.
For this you should remove from these files
platform/cpp/core-test/Makefile.am and
p
Vasiliy Sisko created IGNITE-8321:
-
Summary: Web console: Wrong layout in data storage configuration
of cluster
Key: IGNITE-8321
URL: https://issues.apache.org/jira/browse/IGNITE-8321
Project: Ignite
Hello, Igor.
Still doesn't work.
I removed files you mentioned and got following error messages:
make[3]: вход в каталог
«/home/dragon/src/ignite/modules/platforms/cpp/odbc-test»
CXXLDignite-odbc-tests
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/Scrt1.o: In function
`_start
Igor.
Following settings helps to remove some error, but I still can't make all
things works.
Is it right way to get things work?
```
> export LDFLAGS='-L/usr/lib/x86_64-linux-gnu/'
> export LIBS='-lboost_unit_test_framework'
> libtoolize && aclocal && autoheader && automake --add-missing && aut
Oleg Ostanin created IGNITE-8322:
Summary: Yardstick benchmark preloading option
Key: IGNITE-8322
URL: https://issues.apache.org/jira/browse/IGNITE-8322
Project: Ignite
Issue Type: Improvemen
Alexey Goncharuk created IGNITE-8323:
Summary: Assertion error during simultaneous auto-activation and
manual activation
Key: IGNITE-8323
URL: https://issues.apache.org/jira/browse/IGNITE-8323
Pro
Hello!
I recommend inclusion of this change so that it can make way into 2.5.
Regards,
--
Ilya Kasnacheev
2018-04-19 9:03 GMT+03:00 Petr Ivanov :
> There is not much time left for Apache Ignite 2.5 release, so let’s move
> stage II of packaging architecture implementation (with additional spl
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3864
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3862
---
Pavel Kovalenko created IGNITE-8324:
---
Summary: Ignite Cache Restarts 1 suite hangs with assertion error
Key: IGNITE-8324
URL: https://issues.apache.org/jira/browse/IGNITE-8324
Project: Ignite
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/3876
IGNITE-8092 Put hang on destroy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-8092
Alternatively you can review and apply
Alexey Goncharuk created IGNITE-8325:
Summary: Compressor thread may miss notification on stop
Key: IGNITE-8325
URL: https://issues.apache.org/jira/browse/IGNITE-8325
Project: Ignite
Issu
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/3877
IGNITE-8325 Compressor thread may miss notification on stop
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8325
Hello!
I have also noticed that we seem to miss a Cassandra test suite.
We have a Cassandra module with quite a few tests, but they're not in any
suite.
Maybe we should set one up?
--
Ilya Kasnacheev
2018-04-18 16:42 GMT+03:00 Ilya Kasnacheev :
> Hello!
>
> I've decided to return to this tas
Stepanov Mikhail created IGNITE-8326:
Summary: Can't execute SQL query for create index
Key: IGNITE-8326
URL: https://issues.apache.org/jira/browse/IGNITE-8326
Project: Ignite
Issue Type:
Alexey Goncharuk created IGNITE-8327:
Summary: Node stop hangs because thread sleep blocks gateway lock
Key: IGNITE-8327
URL: https://issues.apache.org/jira/browse/IGNITE-8327
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3779
---
Nikolay,
The code is the same for the attached version to the ticket, as well as the
pull version. The tests are also the same as those provided for the Scala
DF examples. I have checked and they work correctly with the exception of
the path issue which I previously mentioned on the dev list.
I'm
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3878
IGNITE-8327 : Removed delaying CommunicationSpi from test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8327
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/3879
IGNITE-8077 implemented getTxHoldingLockNum and getLockedKeysNum in
TxMXBeanImpl
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apac
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/3800
---
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3880
IGNITE-8324 Update discovery cache as well as topology version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-832
Guys,
We have activity to implement a set of mechanisms to handle critical issues
on nodes (IEP-14 - [1]).
I have an idea to spread message about critical issues to nodes through
entire topology and put it to logs of all nodes. In my view this will add
much more clarity. Imagine all nodes output
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3877
---
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3881
IGNITE-8313 Add trace logs on exchange phases and affinity calculation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
Pavel Tupitsyn created IGNITE-8328:
--
Summary: .NET: Thin client: Run in browser with Blazor
Key: IGNITE-8328
URL: https://issues.apache.org/jira/browse/IGNITE-8328
Project: Ignite
Issue Type
Andrey Kuznetsov created IGNITE-8329:
Summary: Clarify TransactionRollbackException-related paragraph in
documentation
Key: IGNITE-8329
URL: https://issues.apache.org/jira/browse/IGNITE-8329
Proje
Hi Igniters,
It's glad to see our community becomes larger every day. But as it grows it
becomes more and more difficult to manage review and merge processes and
keep quality of our decisions at the proper level. More contributors, more
commits, more components interlinked with each other in subtl
Denis Magda created IGNITE-8330:
---
Summary: Docs: Put JDBC/ODBC URL in Brackets When Connecting From
Bash
Key: IGNITE-8330
URL: https://issues.apache.org/jira/browse/IGNITE-8330
Project: Ignite
Hello, Akmal.
1. As a first step. Let's combine all changes you want to merge into a single
pull request.
I suggest that your changes relates only to "examples" module.
2. So, when you will have one pull request, please, run "Examples" test suite
on Team City for your branch.
After that, attac
Hello, Vladimir.
Thank you for seting up this discussion.
As we discussed, I think an important part of this check list is compatibility
rules.
* What should be backward compatible?
* How should we maintain it?
> 3) If ticket changes public API or existing behavior, at least two commiters
> s
Nikolay Izhikov created IGNITE-8331:
---
Summary: SQL: Add Decimal precision and scale constraint
Key: IGNITE-8331
URL: https://issues.apache.org/jira/browse/IGNITE-8331
Project: Ignite
Issue
Denis/Yury
Can ticket https://issues.apache.org/jira/browse/IGNITE-8242 be included
within 2.5 release?
Upon review of my tickets today, I noticed the fixed version was updated
from 2.5 to 2.6?
This ticket addresses a minor bug in GA Grid.
I have removed method GAGridUtils.getGenesForChromosome
Yuri, Andrey,
Could you have a look and include the ticket into the release?
--
Denis
On Thu, Apr 19, 2018 at 3:23 PM, techbysample wrote:
> Denis/Yury
>
> Can ticket https://issues.apache.org/jira/browse/IGNITE-8242 be included
> within 2.5 release?
> Upon review of my tickets today, I noti
Denis,
I totally agree with you. I'm just not sure why do we need two methods
(init and execute) that have virtually same semantics. With the new design,
what would be the difference between these methods from user point of view,
and how one would determine what exactly should go in each of them?
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3882
Ignite 2.4.4.b3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.4.b3
Alternatively you can review and apply
On Thu, Apr 19, 2018 at 8:19 AM, Yakov Zhdanov wrote:
> Guys,
>
> We have activity to implement a set of mechanisms to handle critical issues
> on nodes (IEP-14 - [1]).
>
> I have an idea to spread message about critical issues to nodes through
> entire topology and put it to logs of all nodes. I
Vasiliy Sisko created IGNITE-8332:
-
Summary: Web console: Empty cells in SQL Scheme table
Key: IGNITE-8332
URL: https://issues.apache.org/jira/browse/IGNITE-8332
Project: Ignite
Issue Type: B
+1
On Thu, Apr 19, 2018 at 5:45 AM, Ilya Kasnacheev
wrote:
> Hello!
>
> I recommend inclusion of this change so that it can make way into 2.5.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-04-19 9:03 GMT+03:00 Petr Ivanov :
>
> > There is not much time left for Apache Ignite 2.5 release, so let
Vasiliy Sisko created IGNITE-8333:
-
Summary: Web console: Editors for table values have wrong baseline
Key: IGNITE-8333
URL: https://issues.apache.org/jira/browse/IGNITE-8333
Project: Ignite
GitHub user VeryFatBoy reopened a pull request:
https://github.com/apache/ignite/pull/3858
IGNITE-7909 - Java code example.
Java version of IgniteDataFrameExample.scala
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/VeryFatBoy/ig
Github user VeryFatBoy closed the pull request at:
https://github.com/apache/ignite/pull/3859
---
Github user VeryFatBoy closed the pull request at:
https://github.com/apache/ignite/pull/3858
---
Github user VeryFatBoy closed the pull request at:
https://github.com/apache/ignite/pull/3858
---
Github user VeryFatBoy closed the pull request at:
https://github.com/apache/ignite/pull/3857
---
GitHub user VeryFatBoy opened a pull request:
https://github.com/apache/ignite/pull/3883
IGNITE-7909 Java code examples are needed for Spark Data Frames.
New source files and test file for Java code examples.
You can merge this pull request into a Git repository by running:
$ g
Nikolay,
Ok. I _think_ it should be better now, so we can try again.
1. I removed the 3 pull requests.
2. I renamed the Java code files with a "Java" prefix.
3. I created a test file for the Java code, using the existing test file
for the Scala code.
4. I updated the TestSuite with bullet #3 abov
58 matches
Mail list logo
