Understood. Will do today.
On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan
wrote:
> On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov wrote:
>
> > Dmitriy,
> >
> >
> > What kind of instructions? Systemd or stand-alone?
> > I thought we have already agreed that systemd services are not eligible
>
On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov wrote:
> Dmitriy,
>
>
> What kind of instructions? Systemd or stand-alone?
> I thought we have already agreed that systemd services are not eligible for
> Windows 10 WSL.
>
> So have I to check that Debian, Ubuntu and SUSE environments for Windows 10
Dmitriy,
What kind of instructions? Systemd or stand-alone?
I thought we have already agreed that systemd services are not eligible for
Windows 10 WSL.
So have I to check that Debian, Ubuntu and SUSE environments for Windows 10
WSL supports running Apache Ignite installed from packages as a
Petr,
I confirm that Ignite starts for me from a downloadable archive on Ubuntu
under Windows 10.
I would actually recommend that instead of discussing here how running
Linux in Windows 10 is not a valid use case, we should probably just test
it and fix it. Can you please try running your
Denis,
The question “will Apache Ignite start under Windows 10 WSL Ubuntu from
packages?” is the same as “will Apache Ignite start under Windows 10 WSL
Ubuntu from binary archive?” concerning running Apache Ignite as standalone
service (from ignite.sh). Did anyone from community tried running
Vladimir,
Can you please explain how our users will be affected? What does it mean to
use "spatial" indexes in Ignite?
D.
On Wed, Jun 6, 2018 at 12:54 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> New H2 version 1.4.197 [1] was released recently. It contain a lot of
> changes (>1000 commits) and
Stop. I've finally figured out what kind of environment Dmitriy is talking
about.
Imagine a Windows developer who needs to run something under Linux on his
machine. He/she would go for VirtualBox and Parallels Desktop. Hope, we
don't have any doubts that it needs to be possible to install Ignite
Pavel,
I'm tried to run an SQL example following the prepared documentation:
https://apacheignite.readme.io/v2.5/docs/nodejs-thin-client#section-examples
Getting an exception below when execute `node SqlQueryEntriesExample.js`
example. Do we support Ignite 2.5 (using its binaries)? Do I need to
Hello Apache Supporters and Enthusiasts
This is a final reminder that our Apache EU Roadshow will be held in
Berlin next week on 13th and 14th June 2018. We will have 28 different
sessions running over 2 days that cover some great topics. So if you are
interested in Microservices, Internet of
First article in a multi-part series.
https://www.gridgain.com/resources/blog/introduction-machine-learning-apache-ignite
Feedback welcome.
Thank you.
Dmitriy Pavlov created IGNITE-8727:
--
Summary: Provide way to test MMap WAL modes failures
Key: IGNITE-8727
URL: https://issues.apache.org/jira/browse/IGNITE-8727
Project: Ignite
Issue Type:
Denis, Alexey, please share you vision.
Sincerely,
Dmitriy Pavlov
вт, 5 июн. 2018 г. в 19:39, Andrey Mashenkov :
> Dmitry,
>
> There are other cases that can result in inconsistent state of Atomic cache
> with 2 or more backups.
>
> 1. For PRIMARY_SYNC. Primary sends requests to all backups
Hello, vbm.
You should add "-DskipTests".
Please, check out [1].
mvn clean install -Pall-java,all-scala,licenses *-DskipTests*
[1]
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ProjectBuild
В Ср, 06/06/2018 в 09:47 -0700, vbm пишет:
> Hi,
>
> When I
Vladimir,
Do agree with you to switch to the new version within 2.7 time frame.
Could you please elaborate on this optimization
>
> Of most
> importance is IN clause optimization which is currently one of our SQL pain
> points.
Should I assume that now H2 considered indexes used within the IN
Hi,
When I try to compile the ignite 2.4 source code with skipTest as false. I a
getting class not found errors.
[ERROR] warning(junit.framework.TestSuite$1) Time elapsed: 0.001 s <<<
FAILURE!
junit.framework.AssertionFailedError:
Exception in constructor: testExchangeOnNodeJoin
Hi!
Can you just not specify -DskipTests as it is default to false?
Also, be warned that with all that enabled profiles you’re going to have
about 50 hours of tests (~47000 units) during build, some of which require
specific JVM options and OS tuning (like PDS or AOP, for example).
On Wed, 6
Denis,
I’ll look into it
On Wed, 6 Jun 2018 at 19:17, Denis Magda wrote:
> I suggest us trying to move the conversation in this direction.
>
> Is it possible to install and run Cassandra using DEB from that emulation
> environment on Windows? If yes, then we should spend our efforts adopting
Ignite mvn compilation with skiptest as false is throwing class not found
errors:
[ERROR] warning(junit.framework.TestSuite$1) Time elapsed: 0 s <<<
FAILURE!
junit.framework.AssertionFailedError:
Exception in constructor: testCreateDropCache
(java.lang.NoClassDefFoundError: Could not initialize
Stanislav Lukyanov created IGNITE-8726:
--
Summary: Highlight that memory metrics are local for a node in the
docs
Key: IGNITE-8726
URL: https://issues.apache.org/jira/browse/IGNITE-8726
Project:
I suggest us trying to move the conversation in this direction.
Is it possible to install and run Cassandra using DEB from that emulation
environment on Windows? If yes, then we should spend our efforts adopting
Ignite for the environment. Otherwise, we should skip it for now.
--
Denis
On Tue,
Hello Tomas,
We've just updated the version of Binutils because Ignite doesn't use this
library directly. So we don't need to inject addBeanIntrospector call.
Binutils are used by some dependencies like Cassandra. Let us confirm that
the dependencies shouldn't be upgraded.
--
Denis
On Wed, Jun
Hi Igniters,
I've tried to use
ignite.scheduler().scheduleLocal(this::checkFailures, "? * * * * *");
Result is
class org.apache.ignite.IgniteException: Current Ignite configuration does
not support schedule functionality (consider adding ignite-schedule module
to classpath).
at
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/4144
IGNITE-8702: Replaced select() with poll() for Linux
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8702
Igniters,
Let's discuss how to implement tests in separate thread. At this point it
is more important to agree on compatibility policies.
On Wed, Jun 6, 2018 at 6:02 PM, Vyacheslav Daradur
wrote:
> Hello, Igniters!
>
> I am not familiar with the Ignite's thin client.
>
> I'd suggest defining
Hello, Igniters!
I am not familiar with the Ignite's thin client.
I'd suggest defining tests scenarios first, to understand what we need
for testing.
For example, our Compatibility Framework may be used for the following scenario:
1. Start node of a previously released version in separate JVM
Ilya Lantukh created IGNITE-8725:
Summary: Make IGNITE_DISABLE_WAL_DURING_REBALANCING enabled by
default
Key: IGNITE-8725
URL: https://issues.apache.org/jira/browse/IGNITE-8725
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4130
---
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/4143
IGNITE-8668 K-fold cross validation of models
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8668
Stanilovsky Evgeny created IGNITE-8724:
--
Summary: Skip logging 3-rd parameter while calling U.warn with
initialized logger.
Key: IGNITE-8724
URL: https://issues.apache.org/jira/browse/IGNITE-8724
Alexey Goncharuk created IGNITE-8723:
Summary: Detect index corruption at runtime
Key: IGNITE-8723
URL: https://issues.apache.org/jira/browse/IGNITE-8723
Project: Ignite
Issue Type:
Denis Dijak created IGNITE-8722:
---
Summary: Issue in REST API 2.5
Key: IGNITE-8722
URL: https://issues.apache.org/jira/browse/IGNITE-8722
Project: Ignite
Issue Type: Bug
Components:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4078
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4091
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4117
---
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4142
IGNITE-8721
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8721
Alternatively you can review and apply these
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2364
---
Hi Vyacheslav,
WDYT about applicability of PDS compatibiltiy framework for thin clients?
Sincerely,
Dmitriy Pavlov
ср, 6 июн. 2018 г. в 13:45, Vladimir Ozerov :
> Hi Nikolay,
>
> Huge +1 for automated compatibility tests. Luckily, we already did that for
> persistence, so probably we can
Vladimir Ozerov created IGNITE-8721:
---
Summary: Third-party security is not integrated with JDBC and ODBC
handlers (thin)
Key: IGNITE-8721
URL: https://issues.apache.org/jira/browse/IGNITE-8721
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4141
IGNITE-8503: Fix IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart test.
WIP. Fix entry startVersion.
You can merge this pull request into a Git repository by running:
$ git pull
Hi Nikolay,
Huge +1 for automated compatibility tests. Luckily, we already did that for
persistence, so probably we can re-use some infrastructure from there.
On Wed, Jun 6, 2018 at 1:20 PM, Nikolay Izhikov wrote:
> +1 From me.
>
> As I wrote in previous mail-threads,
> I think we need to
Pavel Kuznetsov created IGNITE-8720:
---
Summary: SQL: Failed to generate REDUCE query
Key: IGNITE-8720
URL: https://issues.apache.org/jira/browse/IGNITE-8720
Project: Ignite
Issue Type: Bug
+1 From me.
As I wrote in previous mail-threads,
I think we need to create test framework to be able to test compatibility for
all clients we have.
AFAIK, currently, there is no possibility to automatically check compatibility.
В Ср, 06/06/2018 в 11:39 +0300, Vladimir Ozerov пишет:
> Igniters,
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4127
---
Alexey Goncharuk created IGNITE-8719:
Summary: Index left partially built if a node crashes during index
create or rebuild
Key: IGNITE-8719
URL: https://issues.apache.org/jira/browse/IGNITE-8719
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4059
---
Andrey Aleksandrov created IGNITE-8718:
--
Summary: Documentation about using of the C++
BinaryWriter/BinaryReader should be updated
Key: IGNITE-8718
URL: https://issues.apache.org/jira/browse/IGNITE-8718
Alexey Goncharuk created IGNITE-8717:
Summary: Move persisted cache configuration to metastore
Key: IGNITE-8717
URL: https://issues.apache.org/jira/browse/IGNITE-8717
Project: Ignite
Igniters,
I'd like to discuss once again our compatibility policy for thin clients
(.JDBC, ODBC, .NET, Java, etc.). We have no clear rules for now, so let's
try to come to agreement.
Normally database vendors work as follows:
1) There is a set of currently supported database versions
2) There is
Igniters,
New H2 version 1.4.197 [1] was released recently. It contain a lot of
changes (>1000 commits) and some of them are very useful for us. Of most
importance is IN clause optimization which is currently one of our SQL pain
points.
Unfortunately, new version use updated dependency for
49 matches
Mail list logo
