Hello Denis,
Could you, please, add me to the list too: alexzaitzev (Aleksei Zaitsev).
https://ignite.apache.org/community/resources.html
Thanks.
Best regards,
Alex.
15.03.2018, 21:03, "Denis Magda" :
> Dmitriy, Alexey,
>
> Done, now your names are engraved on the page ;)
>
> --
> Denis
>
>
Hi Stan,
I'm 100% for this activity, however I don't think we should change the
behavior of timeouts you listed in #2 - this can lead to unexpected
behavior for users who already use them. I would just deprecate them and
eventually remove.
-Val
On Mon, May 28, 2018 at 1:29 PM, Stanislav
Hi Pavel,
Thank you for pointing to this. We've noticed that, and Ilya K. has already
prepared the fix,
https://issues.apache.org/jira/browse/IGNITE-8604
https://github.com/apache/ignite/pull/4072
If you have some time you can apply the PR, or I will merge it later.
Sincerely,
Dmitriy Pavlov
Hi Dmirty,
IGNITE-5789 merge [1] introduces this bug:
Additional cache is being started from a template (cache name ends with *).
Normally template caches are only started when a cache with matching name
has been requested.
Pavel
[1]
Hi folks,
It looks like we stopped half-way with this activity. I’d like to pick it up.
All seem to agree that we should simplify the timeout settings.
Here are the specific actions I’d like to propose:
1. Promote the use of global timeouts as the best practice
*What*: update the docs to
Hi,
No, there is no Entity Framework Core support for now.
Pavel
On Fri, May 25, 2018 at 10:14 AM, wales wang wrote:
> 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
Ilya Kasnacheev created IGNITE-8633:
---
Summary: Node fails to bail out of wrong BLT, instead hanging
around indefinitely
Key: IGNITE-8633
URL: https://issues.apache.org/jira/browse/IGNITE-8633
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4082
IGNITE-8628: Expose list of SQL (ODBC\JDBC\Thin) clients via JMX.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Anton Kurbanov created IGNITE-8632:
--
Summary: Exception in shutdown routine can prevent JVM shutdown
Key: IGNITE-8632
URL: https://issues.apache.org/jira/browse/IGNITE-8632
Project: Ignite
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4081
IGNITE-8122, IGNITE-8339 Backport to 2.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13804
Alternatively
Andrey Aleksandrov created IGNITE-8631:
--
Summary: IgniteInstanceResource doesn't inject the Ignite instance
to Ignite Predicate during deploying cache with nodeFilter
Key: IGNITE-8631
URL:
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4080
IGNITE-8122 Backport to 2.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13805
Alternatively you can
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/4079
IGNITE-8311: IgniteClientRejoinTest.testClientsReconnectDisabled causâ¦
â¦es exchange-worker to terminate via NPE.
You can merge this pull request into a Git repository by running:
$ git
Welcome to Apache Ignite community!
The problem with your ticket is that it's not clear what value it adds to
the project and how it will improve user experience in general. The problem
you described is rather narrow and I am sure it's possible to find a
workaround without modifying Ignite code.
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4078
IGNITE-8482 2-phase partition release wait optimization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8482
Hello Igniter!
First of all, I'm sorry. I was not aware of the ignite community process
well, so I did not follow the guideline and caused the confusion to the
community.
My name is joungdal.nam and I made the issue as following link.
https://issues.apache.org/jira/browse/IGNITE-6531
Pleases
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4077
IGNITE-8624: Add reproducer to IGNITE-8624 issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ivandasch/ignite ignite-8624
Stanislav Lukyanov created IGNITE-8627:
--
Summary: Verify local partition map against global
Key: IGNITE-8627
URL: https://issues.apache.org/jira/browse/IGNITE-8627
Project: Ignite
Issue
Igor Sapego created IGNITE-8626:
---
Summary: ODBC: Can not compile ODBC with OpenSSL 1.1
Key: IGNITE-8626
URL: https://issues.apache.org/jira/browse/IGNITE-8626
Project: Ignite
Issue Type: Bug
Ivan Rakov created IGNITE-8625:
--
Summary: Dynamic SQL index recreate after cache clear may result
in AssertionError or JVM crash
Key: IGNITE-8625
URL: https://issues.apache.org/jira/browse/IGNITE-8625
Ivan Daschinskiy created IGNITE-8624:
Summary: Add test coverage for NPE in TTL Manager [IGNITE-7972]
Key: IGNITE-8624
URL: https://issues.apache.org/jira/browse/IGNITE-8624
Project: Ignite
Alexey Stelmak created IGNITE-8623:
--
Summary: NPE during cache access
Key: IGNITE-8623
URL: https://issues.apache.org/jira/browse/IGNITE-8623
Project: Ignite
Issue Type: Bug
Max Shonichev created IGNITE-8622:
-
Summary: Zookeeper and TCP discovery SPI' getSpiState method
inconsistent
Key: IGNITE-8622
URL: https://issues.apache.org/jira/browse/IGNITE-8622
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4062
---
Max Shonichev created IGNITE-8621:
-
Summary: TcpDiscoverySpi's UpTime/StartTimestamp methods do not
work
Key: IGNITE-8621
URL: https://issues.apache.org/jira/browse/IGNITE-8621
Project: Ignite
Dmitry Sherstobitov created IGNITE-8620:
---
Summary: Remove intOrder and lc keys from node info in control.sh
--tx utility
Key: IGNITE-8620
URL: https://issues.apache.org/jira/browse/IGNITE-8620
Ivan Fedotov created IGNITE-8619:
Summary: 'Remote node could not start' in ssh connection
Key: IGNITE-8619
URL: https://issues.apache.org/jira/browse/IGNITE-8619
Project: Ignite
Issue Type:
Anghel Botos created IGNITE-8618:
Summary: Support Java 10
Key: IGNITE-8618
URL: https://issues.apache.org/jira/browse/IGNITE-8618
Project: Ignite
Issue Type: Task
Affects Versions: 2.4
GitHub user udaykale opened a pull request:
https://github.com/apache/ignite/pull/4076
IGNITE-8617 Node Discovery Using AWS Application ELB
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/udaykale/ignite IGNITE-8617
29 matches
Mail list logo
