Николай,
It looks a little bit hacky to me. I believe SQL drivers usually use that
approach
as a workaround because there is no other common way to do that.
Sure we can recommend users to use cache.size() or anything other
similar way
to ensure the connection is alive, but it still looks like a w
Hello, Igor.
On the other hand, dedicated `ping` operation makes our API heavier without
adding new feature -
We can do the same with the other part of the API.
Moreover, response to the ping doesn’t mean that SQL or cache query can be
served.
> 14 сент. 2020 г., в 10:08, Igor Sapego написал
Nikolay,
See the discussion on the user list:
1. It is not immediately obvious which APIs perform server calls and which
don't.
2. It is not clear which APIs can cause heavy resource usage on the server
side.
We don't want to stress servers by pinging them.
cache.size() is an example - it
Hello guys,
We've already raised the question about ping requests here [1].
I'm not sure about public API, but at least we can have auto-ping as an
internal mechanism. This will be helpful if the client doesn't send any new
requests but only waits for server-side notifications (for example, if th
Alexey, Andrey, Igniters,
So what do you think? Should we proceed with a 'hacked' version of the
message factory in 2.9 and go for the runtime message generation in later
release, or keep the code clean and fix the regression in the next
releases?
Andrey, can you take a look at my change? I think
Hi folks,
Despite the autocompletion support only for bash, I see the following
benefits from this change:
* It may unify all the CLI tooliing in Ignite, providing a better user
experience
* The library has an ability to generate man pages, which may be nice
* I see there is an open issue for a
Hello!
I've looked through the picocli manual and it looks really great.
We will be able easily add i18n and stuff like this.
Nevertheless, we will get rid of the manual formatting of examples and help
texts.
Kind regards,
Semyon.
14.09.2020, 13:00, "Alexey Goncharuk" :
> Hi folks,
>
> Despite
Sviridov Mikhail created IGNITE-13445:
-
Summary: Yardstick. .jfr server nodes are damaged when the test is
stopped
Key: IGNITE-13445
URL: https://issues.apache.org/jira/browse/IGNITE-13445
Project
Hello! Pls check PR for Yardstick framework.
https://github.com/gridgain/yardstick/pull/38
Good afternoon. About sh stopping the server node from yardstick. Now there are
used commands
pkill -9 -f "Dyardstick. server"
pkill -9 -f "benchmark-server-restarter-start.sh"
the -9 key forcibly termina
Hi! Just a reminder that we will meet this week.
Hope to see you there.
ср, 26 авг. 2020 г. в 01:26, Saikat Maitra :
> Hi Val,
>
> Thank you for scheduling the meetups. Will join and connect on Ignite 3.0
> release planning.
>
> Regards,
> Saikat
>
> On Tue, Aug 25, 2020 at 4:49 PM Valentin Kulic
Dmitrii, seems you are right and we can go with new separate event
пн, 7 сент. 2020 г. в 23:53, Dmitrii Ryabov :
> Any objections to create a separate event, which will be fired before
> executing a query?
>
> ср, 2 сент. 2020 г. в 22:33, Dmitrii Ryabov :
> >
> > I agree with Max, we need to add
Anton Vinogradov created IGNITE-13446:
-
Summary: Configs inside Ducktests logs should be pretty printed
Key: IGNITE-13446
URL: https://issues.apache.org/jira/browse/IGNITE-13446
Project: Ignite
Hello everyone,
I am Sayantanu. I am a programmer with a good grasp on languages like JAVA
, C++ ,Python and Javascript. I love to do competitive programming , web
development and machine learning . I want to contribute to ignite, as this
project matches with my interests. I can contribute to the p
Hi Sayantanu,
Welcome to Apache Ignite Community!
I added your JIRA account to a contributors list. A following page can
help you to start https://ignite.apache.org/community/contribute.html
Looking forward for your contributions!
2020-09-14 7:15 GMT+03:00, Sayantanu Dey :
> Hello everyone,
> I
here is the release:
https://search.maven.org/artifact/io.micronaut.ignite/micronaut-ignite-core/1.0.0.RC1/jar
On Fri, Sep 11, 2020 at 10:16 AM Michael Pollind wrote:
> looks like I was wrong, will have to wait till this PR get merged and a
> release is made in the repo.
>
> https://github.com/m
Maksim Timonin created IGNITE-13447:
---
Summary: Python starter of ducktests
Key: IGNITE-13447
URL: https://issues.apache.org/jira/browse/IGNITE-13447
Project: Ignite
Issue Type: New Feature
Maksim Timonin created IGNITE-13448:
---
Summary: Ducktests selftest: time is synchronized on nodes
Key: IGNITE-13448
URL: https://issues.apache.org/jira/browse/IGNITE-13448
Project: Ignite
Is
Great, Michael! I announced the integration via our twitter channel:
https://twitter.com/ApacheIgnite/status/1305568860964179968?s=20
and we'll work on a technical article a bit later once finish with the
release of the new Ignite docs.
-
Denis
On Mon, Sep 14, 2020 at 10:10 AM Michael Pollind
Maksim Timonin created IGNITE-13449:
---
Summary: Ducktape selftest checks use java from JAVA_HOME
Key: IGNITE-13449
URL: https://issues.apache.org/jira/browse/IGNITE-13449
Project: Ignite
Is
Hello you all!
I am Charles, 19 years old, Java/Kotlin developer, I'm new to open source.
I would like to take any kind of task in order to know the project
better, as I am looking for a topic of interest. My Jira user is 'barddoo'.
Best Regards,
Charles Fonseca.
Ryabov Dmitrii created IGNITE-13450:
---
Summary: Add event fired before query execution
Key: IGNITE-13450
URL: https://issues.apache.org/jira/browse/IGNITE-13450
Project: Ignite
Issue Type: T
Ok, I created a ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-13450
пн, 14 сент. 2020 г. в 14:59, Юрий :
>
> Dmitrii, seems you are right and we can go with new separate event
>
> пн, 7 сент. 2020 г. в 23:53, Dmitrii Ryabov :
>
> > Any objections to create a separate event, which w
22 matches
Mail list logo
