>> Moreover, I don't see a way of implementing such a check. Are you going
to look just for any interface? What about Serializable? Will it do?
The check should look for the interface which implements
"org.apache.ignite.services.Service", it covers the requirement to be
Serializable.
>> For now t
Hello, Igniters.
Ignite right now support `KILL QUERY` command.
I tried to use it and stuck with the simple test.
Error is «Query with provided ID doesn’t exist»
Can you, please, advise me - How KILL QUERY should be used?
```
@Test
public void testCancelSQLQuery() throws Exception {
Hi Prasad,
AFAIK, when value is read through it is not sent to backup nodes. You
can check it using IgniteCache.localPeek method (ask if more details
how to do it are needed).
I usually think about read-through cache for a following case. There
is an underlying storage with "real" data, cache is
Hi Nikolay,
I think that problem here is that the query you are trying to kill is
> "SELECT QUERY_ID FROM SYS.SQL_QUERIES"
itself, which is already completed by the time you run "KILL QUERY" command.
I'm not an expert in the system views, but it seems to me that the line
> List> sqlQries0 = Sq
Denis, Vyacheslav, hi.
What if we just provide an option to disable service metrics at all? It
would keep direct references for local services. Also, we can make service
metrics disabled by default to keep current code working. A warning of
local service issues will be set with the option.
пн, 2
Hi Ivan,
Thank you for the clarification.
So the behavior is same for REPLICATED as well as PARTITIONED cache.
1) Can we please have this behavior documented on Ignite web page? This
will just help users to avoid confusion and design their cache effectively.
2) You said "You can check it using
Hello, Roman.
My initial query was about correct usage of KILL QUERY command.
It seems for me, that It just doesn’t work.
> itself, which is already completed by the time you run "KILL QUERY" command.
As you can see from the source iterator doesn’t closed in the moment of `KILL
QUERY` execution
Nikolay,
> This system view returns queries that are *running* on the node.
> I can see «"SELECT _KEY, _VAL FROM INTEGER» in the results of select.
It looks a bit weird to me, because when I print results of the running
queries from server node:
List> sqlQries0 = SqlViewExporterSpiTest.execute(i
Hello, Roman.
Please, see updated test.
I assert query text to ensure that correct `SELECT` statement used for KILL
command.
This test freeze on «KILL QUERY» execution.
```
@Test
public void testCancelSQLQuery() throws Exception {
startGrids(1);
IgniteEx client = startClientGrid("client
Nikolay,
as I can see, when you run "SELECT * FROM SYS.SQL_QUERIES ORDER BY
START_TIME" from the client node (not from the server node as was in
your first reproducer), the query you are looking for is correctly
returned in the view's result set. Right? So, the problem with this
error message is s
Roman.
> So, the problem with this error message is solved, isn't it?
You are correct.
> The another problem you've encountered after running KILL QUERY command
> with correct qryId is freezing. Am I correct? If yes, this is a known
> issue and I am working on it.
Yes! Thank you for the explana
Roman Kondakov created IGNITE-12732:
---
Summary: SQL: KILL QUERY command hangs on query when query cursor
is held by user or leak
Key: IGNITE-12732
URL: https://issues.apache.org/jira/browse/IGNITE-12732
Nikolay,
I've made a ticket for this issue [1]
> I have one more question.
> Kill query suppose to work as the following:
>
> 1. User execute some SQL statement.
> 2. User waits or fetch query results.
> 2. Other user(or administrator) executes «KILL QUERY» with the query id from
> the step 1.
Maxim Muzafarov created IGNITE-12733:
Summary: File transmission must notify listeners when transmission
ends and resources released
Key: IGNITE-12733
URL: https://issues.apache.org/jira/browse/IGNITE-12733
Hello, Vladimir.
> What if we just provide an option to disable service metrics at all?
I don't think we should create an explicit property for service metrics.
We will implement the way to disable any metrics in the scope of
IGNITE-11927 [1].
> Usage of a proxy instead of service instances can
Aleksey Plekhanov created IGNITE-12734:
--
Summary: Scan query shutting down the node in some cases
Key: IGNITE-12734
URL: https://issues.apache.org/jira/browse/IGNITE-12734
Project: Ignite
Hello, no objections found, plz who can merge it [1]?
[1] https://issues.apache.org/jira/browse/IGNITE-12725
Ignite PMCs,
Hopefully, if not the current release voting, but one of the next one
get success soon we'll get the 2.8.0 release candidate accepted.
To execute the next release scripts for an accepted release candidate
(release_*.sh from a release archive) I need some permissions to
upload a rele
+1 (binding)
I've downloaded the binary archive, run it, checked the ML examples and
JavaDocs.
вс, 1 мар. 2020 г. в 13:49, Ivan Pavlukhin :
> +1 (binding)
>
> Downloaded binary distribution archive, launched a cluster of 2 nodes,
> created/filled/queried a table using sqlline.
>
> A couple of m
Andrey N. Gura created IGNITE-12735:
---
Summary: Metric exporter implementation could lead to
NullPointerException from gauge which invoke communication
Key: IGNITE-12735
URL: https://issues.apache.org/jira/browse
0.
Still can't get access to teamcity links.
пн, 2 мар. 2020 г., 17:24 Alexey Zinoviev :
> +1 (binding)
> I've downloaded the binary archive, run it, checked the ML examples and
> JavaDocs.
>
>
>
> вс, 1 мар. 2020 г. в 13:49, Ivan Pavlukhin :
>
> > +1 (binding)
> >
> > Downloaded binary distribut
Hi Maxim,
This sounds like an option but can take delay the release for more than a
week. Alternatively, someone from the PMC group can execute this step for
you. Is there anybody who can do that?
-
Denis
On Mon, Mar 2, 2020 at 6:21 AM Maxim Muzafarov wrote:
> Ignite PMCs,
>
>
> Hopefully, if
Alex Schrbakov,
As a reviewer, could you merge the changes?
-
Denis
On Mon, Mar 2, 2020 at 6:15 AM Zhenya Stanilovsky
wrote:
>
> Hello, no objections found, plz who can merge it [1]?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12725
>
>
>
Merged to master.
Best regards,
Ivan Pavlukhin
пн, 2 мар. 2020 г. в 18:41, Denis Magda :
>
> Alex Schrbakov,
>
> As a reviewer, could you merge the changes?
>
>
> -
> Denis
>
>
> On Mon, Mar 2, 2020 at 6:15 AM Zhenya Stanilovsky
> wrote:
>
> >
> > Hello, no objections found, plz who can merge it
Denis,
Thank you, I think yes.
But I don't expect that the release will be delayed since we still
need some time for documentation preparation.
On Mon, 2 Mar 2020 at 18:40, Denis Magda wrote:
>
> Hi Maxim,
>
> This sounds like an option but can take delay the release for more than a
> week. Alte
+1 (binding)
* compiled from source.
* start node from bin distribution.
* check thin driver and made some SQL queries with it.
> 2 марта 2020 г., в 17:33, Sergey Antonov
> написал(а):
>
> 0.
> Still can't get access to teamcity links.
>
> пн, 2 мар. 2020 г., 17:24 Alexey Zinoviev :
>
>> +1
Igniters,
Can anyone give permissions to edit\publish documentation Apache
Ignite pages [1]?
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.4.Releasedocumentaiononreadme.io
login: maxmu...@gmail.com
On Mon, 2 Mar 2020 at 18:54, Maxim Muzafarov wrote:
>
> Igniters,
>
>
> Can anyone give permissions to edit\publish documentation Apache
> Ignite pages [1]?
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.4.Releasedocume
I thought documentation can be updated after the release.
Isn’t it?
> Is there anybody who can do that?
I can do it.
> 2 марта 2020 г., в 18:44, Maxim Muzafarov написал(а):
>
> Denis,
>
> Thank you, I think yes.
> But I don't expect that the release will be delayed since we still
> need som
Just made you an administrator of Ignite documentation site.
> 2 марта 2020 г., в 18:54, Maxim Muzafarov написал(а):
>
> login: maxmu...@gmail.com
>
> On Mon, 2 Mar 2020 at 18:54, Maxim Muzafarov wrote:
>>
>> Igniters,
>>
>>
>> Can anyone give permissions to edit\publish documentation Apach
Nikolay, thanks for offering to help with this step of the process. If
Maxim is fine then I would let you publish the artifacts.
The docs should be completed this week and we need to develop the practice
to announce releases only after technical pages are updated and available.
The vote can run in
Folks,
Faced a trouble before resolving the ticket [1]. Fix version is set to
2.8.1 and I suppose some changes from master will be cherry-picked to
2.8.1 branch. Do we have 2.8.1 branch?
Best regards,
Ivan Pavlukhin
пн, 2 мар. 2020 г. в 18:42, Ivan Pavlukhin :
>
> Merged to master.
>
> Best rega
Maxim,
Please stay in touch with Artem If you'd like to release Ignite 2.8 docs.
It's a bit complicated with readme and either Artem can complete this step
or he can collaborate with you letting you experience it. Anyway, before we
release 2.8 version of the docs we need to finish the pages. Here
Ivan,
Unless I missed something, we do not even have a scope for 2.8.1. As I
recall, there were some important changes that did not get to 2.8.0. As the
voting is close to finish, I think we can kick off a discussion for 2.8.1?
Folks,
I think the issue should be merged into the master branch first (2.9).
I pinned some critical issues to 2.8.1 which are, from my point, have
to be fixed in 2.8 but still not due to lack of contributions. Since
the scope for 2.8.1 is not fixed and not discussed yet the goal for
such tasks i
Nikolay,
Thank you for offering help.
I'll back to you tomorrow.
On Mon, 2 Mar 2020 at 18:59, Denis Magda wrote:
>
> Nikolay, thanks for offering to help with this step of the process. If
> Maxim is fine then I would let you publish the artifacts.
>
> The docs should be completed this week and
Vyacheslav,
You can't make service interfaces extend
*org.apache.ignite.services.Service*. Currently it works perfectly if
*org.apache.ignite.services.Service* and a user-defined interface are
independent. This is actually the case in our current examples:
https://github.com/apache/ignite/blob/mas
Agree - this is basically what I meant. We should resolve it as 2.9 and
then form the scope for 2.8.1. Sorry for the confusion.
пн, 2 мар. 2020 г. в 19:26, Maxim Muzafarov :
> Folks,
>
>
> I think the issue should be merged into the master branch first (2.9).
> I pinned some critical issues to 2.
Nikolay Izhikov created IGNITE-12736:
Summary: [IEP-35] Compute task system view doesn't return task
started from remote node
Key: IGNITE-12736
URL: https://issues.apache.org/jira/browse/IGNITE-12736
Dear community,
The vote for a new release candidate is closed, now.
Vote result: The vote PASSES with 6 votes +1 (6 bindings), 0 two votes
and no -1.
+1 votes:
- Denis Magda (binding)
- Anton Vinogradov (binding)
- Pavel Tupitsyn (binding)
- Ivan Pavlukhin (binding)
- Alexey Zinoviev (binding)
Hi Alexey,
Thanks for updating the documentation. The update process is cumbersome as
of now. What will happen is that we will be replacing the content of the
current pages (pre 2.8 pages) with the content from the 2.8 versions. Once
the text is copied manually, a 2.8 version of the page will be d
Emmanouil, thanks, I've reviewed and merged the changes!
-
Denis
On Sun, Mar 1, 2020 at 4:30 PM ReadMe wrote:
> *Emmanouil Gkatziouras* suggested edits to page *Amazon AWS Discovery*.
>
> +++ Added: 27
>
> --- Removed: 2
>
> *Added ALB documentation.*
>
> Documentation for the new Ignite ALB f
Nikolai Kulagin created IGNITE-12737:
Summary: Incorrect annotation on TxDeadlockCauseTest
Key: IGNITE-12737
URL: https://issues.apache.org/jira/browse/IGNITE-12737
Project: Ignite
Issue
43 matches
Mail list logo
