But I want to run the tests against the patch in jira (it is kinda easier to
make changes in the patch). Is that feasible ?
-Original Message-
From: Denis Magda [mailto:dma...@apache.org]
Sent: Friday, December 1, 2017 4:53 AM
To: dev@ignite.apache.org
Subject: Re: ci.ignite.apache: Run
Pavel Konstantinov created IGNITE-7084:
--
Summary: It is possible to generate incorrect configuration using
Basic configuration screen
Key: IGNITE-7084
URL: https://issues.apache.org/jira/browse/IGNITE-7084
Looking at it I see it's blocked by 2701 (which has additional
dependencies, all of which say they are blocked by 2701).
I understand there is an intention to bring the C# client up to par with
the Java client. Is there a ticket/schedule yet for this?
Raymond.
-Original Message-
From: vk
Sunny Chan created IGNITE-7083:
--
Summary: Reduce memory usage of CachePartitionFullCountersMap
Key: IGNITE-7083
URL: https://issues.apache.org/jira/browse/IGNITE-7083
Project: Ignite
Issue Type:
Denis,
Thanks. In review, I noticed that when I edit page:
"https://apacheignite.readme.io/v2.3/docs/genetic-algorithms";, my updates do
not appear instantly.
Is this the correct behavior of ReadMe?
I assumed that updates were 'instant' akin to blogging..
Please advise.
Regards,
Turik
--
Val,
Sounds reasonable to me. The fewer useless and potentially harmful features or
“switches” we have in Ignite the clear it will be for the user how to use us in
a right way.
+1 for the deprecation and further removal.
—
Denis
> On Nov 30, 2017, at 3:07 PM, Valentin Kulichenko
> wrote:
>
Cergey,
You need to run the tests agains the pull-request. In your case it should be
this one - pull/2970/merge
—
Denis
> On Nov 30, 2017, at 12:36 PM, Cergey wrote:
>
> Probably, I missed something in the patch
> (https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not (and
>
Hi Dmitriy,
I’m totally for the FailureProcessingPolicy addition to IgniteConfiguration.
Apart of this, may I ask you to create corresponding documentation tickets for
2.4 release and “documentation” component? Only for the improvements that are
getting into the next release. Basically you can
So for what it's worth more and more of Spark's own services have also
moved to be in separate processes, and with the increased work around
scaling the executors are going to continue this trend.
On Thu, Nov 30, 2017 at 3:07 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Ignit
Igniters,
Currently we claim to support IgniteRDD in two modes: standalone and
embedded. Standalone means there is a separately running Ignite cluster,
and Spark start client node(s) to interact with it. In embedded node
everything runs within Spark, including Ignite server nodes that are
started
It sounds like a bug, get() from backup should update the local map.
Andrey, please feel free to file a ticket.
On Thu, Nov 30, 2017 at 1:41 AM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:
> Hi Igniters,
>
> Ignite Replicated cache with CacheStore and Read-through=true and
> ReadFromBac
Valentin,
Now it's run OK.
Thank you.
30.11.2017 23:41, Valentin Kulichenko пишет:
Nikolay,
Please try once again.
-Val
On Thu, Nov 30, 2017 at 11:43 AM, Николай Ижиков mailto:nizhikov@gmail.com>> wrote:
Valentin,
Thank you, but your changes does not enough
I ran a build
Nikolay,
Please try once again.
-Val
On Thu, Nov 30, 2017 at 11:43 AM, Николай Ижиков
wrote:
> Valentin,
>
> Thank you, but your changes does not enough
>
> I ran a build for my branch and still has "Unsupport major.minor version
> 52.0" issue [1]
>
> Build log:
>
> `Starting: /usr/lib/jvm/jav
Great! Let me know if you need any assistance and/or intermediate review.
-Val
On Thu, Nov 30, 2017 at 12:05 AM, Николай Ижиков
wrote:
> Valentin,
>
> > Can you please create a separate ticket for the strategy implementation
> then?
>
> Done.
>
> https://issues.apache.org/jira/browse/IGNITE-707
Probably, I missed something in the patch
(https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not (and did
not) start automatically. What may be wrong ?
-Original Message-
From: Cergey [mailto:cossa...@mail.ru.INVALID]
Sent: Friday, December 1, 2017 12:31 AM
To: dev@ignit
Hi, igniters,
When trying to run "Run all for patch" build with parameter "jira number"
(existing, e.g. IGNITE-6745 or random), build fails
(https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAllTestBuilds)
with exception: java.net.ConnectException: Connection timed out. I
+1
On Thu, Nov 30, 2017 at 11:29 AM, Denis Magda wrote:
> Igniters,
>
> Considering that we’re going to support Java 9 in the next release and
> hitting several limitations caused by current Java 7 support (see spark
> issue [2] and account difficulties of Java 8 based ML development) I would
>
Valentin,
Thank you, but your changes does not enough
I ran a build for my branch and still has "Unsupport major.minor version 52.0"
issue [1]
Build log:
`Starting: /usr/lib/jvm/java-7-oracle/bin/java
-DJAVA_HOME=/usr/lib/jvm/java-8-oracle`
I look to build settings and found some variables
Igniters,
Considering that we’re going to support Java 9 in the next release and hitting
several limitations caused by current Java 7 support (see spark issue [2] and
account difficulties of Java 8 based ML development) I would propose to
discontinue Java 7.
Let’s do both things in AI 2.4: Jav
Nikolay,
Java 7 support will be dropped by Ignite soon, so let's do the upgrade now.
I changed both 'Ignite RDD' and 'Ignite RDD spark 2_10' configuration on TC
to use JDK 8. Can you try it out and let me know if it works?
-Val
On Wed, Nov 29, 2017 at 11:28 PM, Николай Ижиков
wrote:
> Valentin
Hi, Igniters!
We have a set of internal problems, which required graceful node shutdown,
or other reaction configured (See discussion thread
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Enhancement-Proposal-7-Internal-problems-detection-td24460.html
):
- IgniteOutOfMemoryException
Hi Dmitriy,
We're still working on the documentation of LLPL. You may forward me your
questions in the meantime and I'll try to answer them.
Thanks,
Mulugeta
-Original Message-
From: Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
Sent: Thursday, November 16, 2017 1:26 PM
To: dev@igni
Pavel Tupitsyn created IGNITE-7082:
--
Summary: .NET: Cross-platform standalone executable
Key: IGNITE-7082
URL: https://issues.apache.org/jira/browse/IGNITE-7082
Project: Ignite
Issue Type: I
Joel Lang created IGNITE-7081:
-
Summary: Increase in partition count silently breaks persistent
cache reads and writes
Key: IGNITE-7081
URL: https://issues.apache.org/jira/browse/IGNITE-7081
Project: Igni
Ilya Kasnacheev created IGNITE-7080:
---
Summary: YARN fails to create containers if Bash functions
exported in environment
Key: IGNITE-7080
URL: https://issues.apache.org/jira/browse/IGNITE-7080
Proje
Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/3035
---
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/3118
ignite-7049
Optimistic transaction is not properly rolled back if timed out before
sending prepare response.
You can merge this pull request into a Git repository by running:
$ git pull
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3106
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3098
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3067
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2980
---
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/3117
IGNITE-6880: KNN Regression and Classification
Also added Labeled Dataset and loading from txt file
You can merge this pull request into a Git repository by running:
$ git pull https://github
Aleksey Zinoviev created IGNITE-7079:
Summary: Add examples for kNN classification and for kNN regression
Key: IGNITE-7079
URL: https://issues.apache.org/jira/browse/IGNITE-7079
Project: Ignite
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/3105
---
Alexander Belyak created IGNITE-7078:
Summary: *Names() API for datastructures
Key: IGNITE-7078
URL: https://issues.apache.org/jira/browse/IGNITE-7078
Project: Ignite
Issue Type: Wish
Seems,
We have to use custom discovery message to are about new nodes that joining
grid.
On Thu, Nov 30, 2017 at 5:08 AM, Alexey Kuznetsov
wrote:
> Alex,
>
> We have such issue in JIRA: https://issues.apache.org/
> jira/browse/IGNITE-369
> I think you can update its description after we agreed
I would start with communication only, and put discovery and clients aside
for now. Let's confirm that communication works well with compression first
in terms of performance.
On Thu, Nov 30, 2017 at 10:36 AM, Nikita Amelchev
wrote:
> Hello, everybody.
> I propose the following design for networ
Hi Igniters,
Ignite Replicated cache with CacheStore and Read-through=true and
ReadFromBackup=true works in unexpected way from user perspective.
Imagine a case user have a large dataset in underlying db and want to cache
hot data only, so there is no need to do cache.loadCache().
User expectati
Github user dmekhanikov closed the pull request at:
https://github.com/apache/ignite/pull/2929
---
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/3116
ignite-6369 fix Scala version for ignite-spark dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6
Hi Alexey,
1,2,3 are related only to handshake. All other operations are consistent.
Handshake request format is dictated by existing client connector that is
shared with ODBC and JDBC clients (see
ClientListenerNioListener.onHandshake).
so we can't add magic numbers or change operation code.
Bu
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3115
IGNITE-6423: PDS could be corrupted if partition have been evicted and
owned again
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
Hi Pavel,
Let me add my 5 cents.
1. It would be great if both Handshake request & response have some "magic"
number (2 or 4 bytes) inside their msg body. That will simplify handling
situations when non-Ignite client connects to Ignite server and vice versa.
2. It makes sense to add server ve
Hi, Igniters!
I've prepared PR [1] for the issue IGNITE-6612 "Wrap ack methods in their
own class" [2] . TeamCity tests look good [3]. Could someone review it?
Thanks in advance!
[1]https://github.com/apache/ignite/pull/3046
[2]https://issues.apache.org/jira/browse/IGNITE-6612
[3]
https://ci.ignite
Valentin,
> Can you please create a separate ticket for the strategy implementation then?
Done.
https://issues.apache.org/jira/browse/IGNITE-7077
> Any idea on how long will it take?
I think it will take 2-4 weeks to implement such a strategy.
I try my best to make a ready to review PR before
Nikolay Izhikov created IGNITE-7077:
---
Summary: Spark Data Frame Support. Convert complete query to
Ignite SQL
Key: IGNITE-7077
URL: https://issues.apache.org/jira/browse/IGNITE-7077
Project: Ignite
46 matches
Mail list logo