Hello, Igniters.
I want to organize the webinar for the Apache Ignite community.
The subject of the webinar - «New monitoring and system view in 2.8»
Is there any Apache guides on how to do it?
What software should be used? How I should announce it? etc...
Igor Seliverstov created IGNITE-12776:
-
Summary: Calcite integration. An exception occurred when a
replicated cache is used in a query.
Key: IGNITE-12776
URL: https://issues.apache.org/jira/browse/IGNITE-12776
yiteng.liu created IGNITE-12777:
---
Summary: Incorrect query result with count(*) should return 0
Key: IGNITE-12777
URL: https://issues.apache.org/jira/browse/IGNITE-12777
Project: Ignite
Issue T
It's the perfect idea. Will it in English?
чт, 12 мар. 2020 г. в 10:15, Nikolay Izhikov :
> Hello, Igniters.
>
> I want to organize the webinar for the Apache Ignite community.
> The subject of the webinar - «New monitoring and system view in 2.8»
>
> Is there any Apache guides on how to do it?
>
Yes.
> 12 марта 2020 г., в 10:59, Maksim Stepachev
> написал(а):
>
> It's the perfect idea. Will it in English?
>
> чт, 12 мар. 2020 г. в 10:15, Nikolay Izhikov :
>
>> Hello, Igniters.
>>
>> I want to organize the webinar for the Apache Ignite community.
>> The subject of the webinar - «New
Nikolay Izhikov created IGNITE-12778:
Summary: KILL QUERY command doesn't close already fetched cursor
Key: IGNITE-12778
URL: https://issues.apache.org/jira/browse/IGNITE-12778
Project: Ignite
Vladimir Steshin created IGNITE-12779:
-
Summary: Split Ignite and IgniteMXBean, make different behavior of
the active(boolean)
Key: IGNITE-12779
URL: https://issues.apache.org/jira/browse/IGNITE-12779
Andrey, hi.
>> We won’t affect existing services
How exactly will we affect services without special interface? Please see
the benchmarks in previous email.
>>> what if we generate will generate proxy that collects service’s metrics
only if service will implement some special interface?
I don
Hi igniters,
There are the following functions. I haven't found the related
documents. Please confirm again?
1.SQL:Added KILL QUERY command
2.SQL:Added ability to specify query parallelism in CREATE TABLE's WITH
"" clause
3.SQL:Added default query timeout
4.JDBC:Added cache expiry policie
Good afternoon!
I send PR for ticket: https://issues.apache.org/jira/browse/IGNITE-8152
Vladislav Pyatkov created IGNITE-12780:
--
Summary: Deadlock between db-checkpoint-thread and
checkpoint-runner
Key: IGNITE-12780
URL: https://issues.apache.org/jira/browse/IGNITE-12780
Project: Ig
The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.8.0.
Apache Ignite® is an in-memory computing platform for transactional,
analytical, and streaming workloads delivering in-memory speeds at
petabyte scale.
https://ignite.apache.org
Apache Ignite community rolled
Hi ,
Did anyone get a chance to look at this ?
Summary of the issue I am facing. :
We have a 3 node server cluster
A 4th node joins as a client with a continuous query on a Table A(
Transaction_mode = transactional ).
Now If I bring the client down and issue an update to the Table A within
fai
Veena Mithare created IGNITE-12781:
--
Summary: Cache_Put event generated from a remote_client user
action has subject uuid of Node that executes the request sometimes.
Key: IGNITE-12781
URL: https://issues.apache.
HI ,
Created this jira :
https://issues.apache.org/jira/browse/IGNITE-12781
regards,
Veena.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Igniters,
Let's start a discussion about the next Apache Ignite 2.8.1 bugfix
release. The following things need to be discussed:
- time/deadlines
- scope of the release
- a release manager candidate
My personal vision that the 2.8.1 release is a bugfix release, so
`improvement` issues are no
Hello!
I have marked https://issues.apache.org/jira/browse/IGNITE-12672 to 2.8.1
since it is an important Spring Data issue with trivial fix.
"Query annotations are not working if statement keywords are in lower case"
We should make sure that all fixes in 2.8.1 also end up in master - needs
to b
Hi!
I don't see https://issues.apache.org/jira/browse/IGNITE-12582 in future
release plan. Append it too, please
On Thu, 12 Mar 2020 at 17:12, Ilya Kasnacheev
wrote:
> Hello!
>
> I have marked https://issues.apache.org/jira/browse/IGNITE-12672 to 2.8.1
> since it is an important Spring Data is
Hello, Igniters.
I propose to add these tickets to the 2.8.1 scope
[1] Disallow silent deactivation in CLI and REST -
https://issues.apache.org/jira/browse/IGNITE-12701
[2] Compute job system view - https://issues.apache.org/jira/browse/IGNITE-12745
[3] Transaction operations metrics -
https://
Hi, Igniters!
I propose to discuss immediately the timing of 2.9.0 and interim releases!
My propose:
~ June 01 - 2.8.1
~ September 01 - 2.8.2
~ November 01 - 2.9.0
Sberbank team, for its part, is ready to take on the work of management
interim releases.
Regards,
Aleksey Chetaev.
--
Sent fro
I thought the release cycle should be community driven, not single donator.
Should not 2.8.1 be bug fixing / stabilising release with release date as soon
as all issues are resolved?
Also — what's the haste with next minor version? Cannot we deliver next fix
versions with per-feature release cyc
Great dates for released, I support mr. Chetaev
чт, 12 мар. 2020 г., 17:38 Aleksey Chetaev :
> Hi, Igniters!
> I propose to discuss immediately the timing of 2.9.0 and interim releases!
> My propose:
> ~ June 01 - 2.8.1
> ~ September 01 - 2.8.2
> ~ November 01 - 2.9.0
>
> Sberbank team, for its p
Hello, Petr.
> I thought the release cycle should be community driven, not single donator.
We are the part of the global Ignite community, itn’t it?
If you know some reason to postpone bug fix releases, please, write it down.
> what's the haste with next minor version?
Users of the Ignite acti
I don’t see the donator desire here. This desire is to give AI consumers more
frequent releases with bug fix and understanding when we, as a community,
will release new, announced features to them.
Now it’s not clear why consumers should fix bugs themselves, if they don’t
have the opportunity to g
Alexey,
> Now it’s not clear why consumers should fix bugs themselves if they don’t
> have the opportunity to get the expected delivery time.
Fully agree.
Users should see the release plan for the current year.
On Thu, 12 Mar 2020 at 18:16, Aleksey Chetaev wrote:
>
> I don’t see the donator de
Hello, Igniters.
I propose to cherry-pick this bug-fix ticket to the 2.8.1:
IGNITE-12728 The cache#putAllAsync method does not collect statistics [1]
[1] https://issues.apache.org/jira/browse/IGNITE-12728
чт, 12 мар. 2020 г. в 18:27, Maxim Muzafarov :
>
> Alexey,
>
> > Now it’s not clear why co
Folks,
Not sure that we will be moving in the right direction discussing dates
with no clarity of what is to be released in a specific version. Instead,
let's talk out our plans/tasks first and then put them on a timeline. That
certainly applies to big releases such as 2.9 that deserve a separate
Nikolay, I believe we can use Gotowebinar (as GridGain contribution) or as
well GoToMeeting. I will be happy to help with the announcement and
scheduling.
Dmitry, what do you think? ASF slack looks less comfortable for this
purpose.
чт, 12 мар. 2020 г. в 11:22, Nikolay Izhikov :
> Yes.
>
> > 12 м
Aleksey,
> My propose:
> ~ June 01 - 2.8.1
> ~ September 01 - 2.8.2
> ~ November 01 - 2.9.0
What is your motivation for such release schedule? I believe release
should be features/fixes driven not by time/deadline driven.
We can release 2.8.x versions every week yet (as maintenance
releases). Bu
Hello!
But why the node was down?
Was it due to failure handler? Unhandled exception in critical thread?
Anything else? Did you find any work-around?
I have not heard about Continuous Query issues such as the one you are
describing, and I suggest filing an IGNITE ticket with details.
Regards,
-
Nikolay,
That's an excellent idea. As Kseniya mentioned, there is plenty of tools
for such events - gotomeeting/webinar, zoom, etc. I have not heard that ASF
guides using any, it's up to us.
Also, I'll be doing a generic webinar about 2.8 (check this discussion [1])
featuring the new metrics syst
Hi Nikolay, Ksenia,
All webinars I remember were conducted using GridGain's GoToMeeting
account. AFAIK, Apache Foundation does not provide some shared account for
running webinars. I don't see any issues if a company will sponsor the
infrastructure for running community - related activity. I hope
Dmitriy, Kseniya, thanks for the answers.
> 12 марта 2020 г., в 19:25, Dmitriy Pavlov написал(а):
>
> Hi Nikolay, Ksenia,
>
> All webinars I remember were conducted using GridGain's GoToMeeting
> account. AFAIK, Apache Foundation does not provide some shared account for
> running webinars. I d
Nikolay,
Choose whatever is comfortable for you. I prefer Gotowebinar, but youtube
streaming, for example, is also fine. I will be glad to help with
announcements and testing the translation. Let's keep in touch.
чт, 12 мар. 2020 г. в 19:29, Nikolay Izhikov :
> Dmitriy, Kseniya, thanks for the a
Igniters,
With the final 2.8 release steps checked out today by announcing the
version globally (congrats!), it's a proper time to consider and tweak our
release process, making completion of some phases more predictable and
aligned. I would like to dedicate this thread solely to changes related t
Hi,
I used ignite in version 2.7.6 (but I have also seen this behaviour on
other 2.7.x versions) and there aren't any near or local cache.
I expect that if I ask distributed cache about key which does not exist
then the miss metric will be incremented.
śr., 11 mar 2020 o 11:35 Andrey Gura napisa
Hi,
> There are the following functions. I haven't found the related documents.
> Please confirm again?
Thank you for checking this thoroughly! I looked into SQL and JDBC items.
> 1.SQL:Added KILL QUERY command
Here it is https://apacheignite-sql.readme.io/docs/kill-query but it
seems no link f
37 matches
Mail list logo