Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4063
---
Igniters,
There are a couple of events coming up on May 30 – one is a webinar and another
is a meetup in San Francisco.
Denis Magda will host a free one-hour webinar on May 30. It's Part 1 of a
2-part series titled: “Adding Speed and Scale to Existing Applications with No
Rip and
Hi Dmitriy,
Agree, your proposal makes a lot of sense.
p.
On Fri, May 25, 2018 at 11:04 AM, Dmitriy Setrakyan
wrote:
> I generally think that as a community we need to start taking an approach
> of separate thin client releases. This goes for Java, .NET, JDBC, ODBC,
>
I generally think that as a community we need to start taking an approach
of separate thin client releases. This goes for Java, .NET, JDBC, ODBC,
Node.JS, etc...
We can still host them in the same Ignite repo, but they should be a
separate download. Of course, they should be included in the
Hello Dmitriy and welcome!
You're in. Feel free to assign the ticket to your account.
--
Denis
On Fri, May 25, 2018 at 8:25 AM, Dmitriy Gladkih
wrote:
> Hello Ignite Community!
>
> My name is Dmitriy. I want to contribute to Apache Ignite and want to start
> with
Hi, guys:
I want to used Apache.Ignite.EntityFramework in the .net core 2.0, but
this component does not support .net core 2.0.
Is there a version of.net core 2.0 that will be supported?
Waiting for your reply.
Thanks.
+1 (binding)
On Fri, May 25, 2018 at 8:05 AM, Dmitry Pavlov
wrote:
> +1 (Non Binding)
>
> I've checked
> ver. 2.5.0#20180523-sha1:86e110c7
> with Ignite TC helper (tool for MTCGA reports and monitoring).
>
> DB data was restored successfully, tool is full operational on
GitHub user kreig133 opened a pull request:
https://github.com/apache/ignite/pull/4075
Ignite 6284
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6284
Alternatively you can review and apply these
Hello Ignite Community!
My name is Dmitriy. I want to contribute to Apache Ignite and want to start
with this issue - IGNITE-8603, my JIRA username "dgladkikh".
Thanks!
Igniters,
While making review I checked next main-method tests:
org.apache.ignite.loadtests.mapper.GridContinuousMapperLoadTest1
org.apache.ignite.loadtests.mapper.GridContinuousMapperLoadTest2
And I have found that they are totally outdated!
They use config which was changed a long time ago.
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/4074
IGNITE-8293 BinaryUtils#isCustomJavaSerialization fails when only
readObject is declared in a class
You can merge this pull request into a Git repository by running:
$ git pull
+1 (Non Binding)
I've checked
ver. 2.5.0#20180523-sha1:86e110c7
with Ignite TC helper (tool for MTCGA reports and monitoring).
DB data was restored successfully, tool is full operational on Ignite 2.5
version.
пт, 25 мая 2018 г. в 12:25, Иван Артюхов :
> +1
>
> OS: Ubuntu
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4046
---
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/4071
IGNITE-8495: Implement C++ thin client start and connection establishment.
You can merge this pull request into a Git repository by running:
$ git pull
Hi Igniters,
recently we've got 60-70 new test failures in .NET
For me it is not simple to say which commit has failed build, so I suggest
the following:
1. Add Platform .NET tests to run-all basic, it will be started by
per-VCS-commit basis. Per commit run will indicate change which failed the
GitHub user a-polyakov opened a pull request:
https://github.com/apache/ignite/pull/4069
IGNITE-8467 fix filter minSize for transactions utility control.sh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/a-polyakov/ignite
Hi Ray,
Have you found the solution? This is interesting question for me too.
Breafly search leads me to this file:
\ignite\config\ignite-log4j.xml
as it described here:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/logger/log4j/Log4JLogger.html
with (and other DEBUG
+1
OS: Ubuntu 17.10 (Linux 4.13.0-41-generic amd64)
JRE: 1.8.0_171-b11 (Oracle)
Build Ignite Fabric from sources (without .NET and LGPL deps): OK
Build RPM and DEB packages: OK
Start ignite.sh: OK
Run several 'datagrid', 'sql' and 'persistentstore' examples: OK
2018-05-25 10:29 GMT+03:00
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4037
---
Denis Garus created IGNITE-8614:
---
Summary: The atomic cache in inconsistent state
Key: IGNITE-8614
URL: https://issues.apache.org/jira/browse/IGNITE-8614
Project: Ignite
Issue Type: Task
+1 (binding)
Download sources: OK.
Build from sources: OK
Start ignite.bat: OK
Build and start Web Console from sources in DEV mode: OK
--
Alexey Kuznetsov
GitHub user qiuxiaoj opened a pull request:
https://github.com/apache/ignite/pull/4068
Update release-web-agent.xml
I get a error `-bash: ./ignite-web-agent.sh: /bin/bash^M: bad interpreter:
No such file or directory` if run the script `ignite-web-agent.sh` on Ubuntu
18.04. The
Ilya Borisov created IGNITE-8613:
Summary: Web console: investigate E2E tests on Node.js 10
Key: IGNITE-8613
URL: https://issues.apache.org/jira/browse/IGNITE-8613
Project: Ignite
Issue
23 matches
Mail list logo