Good afternoon!
> On Nov 8, 2017, at 1:11 PM, Sérgio Manuel Pereira Simões
> wrote:
>
> Hello
Oleg,
The JIRA permissions were granted. Please go ahead and pick a ticket you like.
—
Denis
> On Nov 7, 2017, at 11:12 PM, Олег Салахутдинов wrote:
>
> Hello Denis,
>
> My JIRA id is of.salakhutdinov and I am planning to resolve bugs.
>
>
> Best regards,
> Oleg Salakhutdinov.
>
>
> Сред
Hi there,
I have started to work on segmentation checks and noticed that we are
missing a method from IgniteConfiguration which could be useful.
For example let say we have 3 segmentation resolver and we want all of them
to be passed we set the setAllSegmentationResolversPassRequired(true) but
wh
Yakov,
Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-6847
Feel free to add if I missed anything.
-Val
On Tue, Oct 10, 2017 at 3:22 AM, Yakov Zhdanov wrote:
> Val, I really like your idea to implement common mechanism for all APIs.
> Can you please file a ticket?
>
> --Yakov
Valentin Kulichenko created IGNITE-6847:
---
Summary: Add an ability to provide custom per operation context
Key: IGNITE-6847
URL: https://issues.apache.org/jira/browse/IGNITE-6847
Project: Ignite
Andrey,
I think you're right. This logic was once refactored so that actual
execution happens only when cursor iteration starts, and I guess metrics
were not fixed accordingly. Can you file a ticket?
-Val
On Wed, Nov 8, 2017 at 9:27 AM, Andrey Kornev
wrote:
> (Changed the subject to maybe make
On Thu, Nov 9, 2017 at 5:06 AM, Timothy Steffens wrote:
> Can the JMSStreamer be configured to inspect the message prior to picking
> it off of the queue? If so, then I can use multiple JMSStreamers as you
> suggest. If not, then I cannot since each JMSStreamer will not know if the
> next message
Can the JMSStreamer be configured to inspect the message prior to picking it
off of the queue? If so, then I can use multiple JMSStreamers as you suggest.
If not, then I cannot since each JMSStreamer will not know if the next message
is for them or for another to process. I do not want to have
Hello
Valentin Kulichenko created IGNITE-6846:
---
Summary: Add metrics for entry processor invocations
Key: IGNITE-6846
URL: https://issues.apache.org/jira/browse/IGNITE-6846
Project: Ignite
Is
Tim,
I am not sure why we need to change the JMS streamer. Why not just create a
separate JMS streamer per cache? In my view, it is more intuitive to keep
one-to-one relationship between JMS streamer and the data streamer.
D.
On Wed, Nov 8, 2017 at 9:40 AM, Timothy Steffens <
timothy.steff...@ya
Andreas Weber created IGNITE-6845:
-
Summary: WebSessionFilter cannot handle liberty session ids
Key: IGNITE-6845
URL: https://issues.apache.org/jira/browse/IGNITE-6845
Project: Ignite
Issue T
(Changed the subject to maybe make people actually read the posting.)
Anyway, if somebody (who knows that code) could take a quick look to see if the
duration is indeed computed correctly (or not), that would be greatly
appreciated!
Thanks
Andrey
From:
GitHub user anton-vinogradov opened a pull request:
https://github.com/apache/ignite/pull/3004
Ignite 6411 benchmark
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6411-benchmark
Alternatively you
Hello, Denis.
I know about this issue.
I can try to fix it.
But, seems that ticket assigned to you, currently.
Let me know if you need some kind of help.
2017-11-08 18:17 GMT+03:00 Николай Ижиков :
> Привет.
>
> Я знаю об этой проблеме. Натолкнулся на неё при реализации Spark DataFrame
> API
Hi,
I granted contributor access for you in JIRA.
Looking forward for your contributions!
On Wed, Nov 8, 2017 at 9:49 PM, Kirill Shirokov
wrote:
> Dear Ignite Community,
>
> My name is Kirill Shirokov and I would like to make contributions to Apache
> Ignite.
>
> Would it be possible to acces
Igniters,
I noticed a problem in POM files of *ignite-spark* and *ignite-spark_2.10*
modules.
*ignite-spark* is targeted to be used by Scala 2.11, while
*ignite-spark_2.10* is made for Scala 2.10.
*But, **ignite-spark* has *spark-unsafe_2.10* as a dependency, and
*ignite-spark_2.10* depends on *
GitHub user ybabak opened a pull request:
https://github.com/apache/ignite/pull/3003
IGNITE-6762: SparseDistributedMatrixExample failed with NPE.
Fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
Dear Ignite Community,
My name is Kirill Shirokov and I would like to make contributions to Apache
Ignite.
Would it be possible to access Apache Ignite JIRA? My user name is
'kirill.shirokov'.
Thank you in advance!
Kind regards,
Kirill
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/3002
Ignite 2.1 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1-master
Alternatively you can review and a
Pavel Pereslegin created IGNITE-6844:
Summary: Additional JMX metrics for cluster monitoring.
Key: IGNITE-6844
URL: https://issues.apache.org/jira/browse/IGNITE-6844
Project: Ignite
Issue
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3001
IGNITE-6840
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6840
Alternatively you can review and apply these
Vladimir Ozerov created IGNITE-6843:
---
Summary: SQL: optionally do not use WAL when executing CREATE INDEX
Key: IGNITE-6843
URL: https://issues.apache.org/jira/browse/IGNITE-6843
Project: Ignite
Hi,
Added you to the contributors list. Please go ahead and assign the tickets
on yourself.
On Wed, Nov 8, 2017 at 4:20 PM, Alex Plehanov
wrote:
> Hello Ignite Community!
>
>
> My name is Aleksey. I want to contribute to Apache Ignite and want to start
> with implementation of some JMX metrics.
Hello Ignite Community!
My name is Aleksey. I want to contribute to Apache Ignite and want to start
with implementation of some JMX metrics. Please add me as contributor.
My account in JIRA is "alex_pl".
Thanks!
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2999
---
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/3000
ignite-6767: reset of the topVer on loading of the entry
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sk0x50/ignite ignite-6767-master
Alter
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/2999
Fixed licensed header
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6737fix
Alternatively you can review an
Yakov, thanks for your suggestion.
I will create such MBean to include these metrics.
2017-11-07 20:11 GMT+03:00 Yakov Zhdanov :
> This seems to be incorrect place for implementing it. I would think of
> something more generic like IgniteClusterMBean. It should also work for any
> implementation
Alexei Scherbakov created IGNITE-6842:
-
Summary: Stop all nodes after test by default.
Key: IGNITE-6842
URL: https://issues.apache.org/jira/browse/IGNITE-6842
Project: Ignite
Issue Type:
Github user ntikhonov closed the pull request at:
https://github.com/apache/ignite/pull/2983
---
Denis/Yury,
I updated my previous post slightly,
For clarity, Please simply respond to this post and disregard previous.
Upon review of your previous comments, please respond to my feedback :
1. I believe GA Grid can be implemented in separate package within ML
library and operate independen
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2998
Ignite-gg-13021
Fixed possible NPE on node stop.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13021-maste
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/2997
IGNITE-6835 ODBC driver should handle ungraceful tcp disconnects
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/2996
BaselineAffinityTopology
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-blt-merge
Alternatively yo
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2995
IGNITE-6841: Increased ODBC protocol version for multiple statements.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ig
Igor Sapego created IGNITE-6841:
---
Summary: ODBC: Add new version for multiple result set
functionality
Key: IGNITE-6841
URL: https://issues.apache.org/jira/browse/IGNITE-6841
Project: Ignite
I
GitHub user andreaswe opened a pull request:
https://github.com/apache/ignite/pull/2994
WebSessionFilter can handle liberty session ids
## Problem:
Websphere Liberty creates session ids in the following form (way the
session id is serialized in the cookie):
\\:\
e.g. 00
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2934
---
39 matches
Mail list logo
