But internally the SQL query still runs on some cache, no? What happens to
the metrics accumulated on that cache?
D.
On Thu, Aug 16, 2018, 18:51 Alexey Kuznetsov wrote:
> Dima,
>
> "cache-less" means that SQL executed directly on SQL engine.
>
> In previous version of Ignite we execute queries
Is there a blocker ticket for 2.7?
On Thu, Aug 16, 2018, 19:59 Denis Magda wrote:
> Igniters,
>
> Was troubleshooting an Ignite deployment today and couldn't find out from
> the logs what was the actual off-heap space used.
>
> Those were the given memory resoures (Ignite 2.6):
>
> [2018-08-16
Igniters,
Was troubleshooting an Ignite deployment today and couldn't find out from
the logs what was the actual off-heap space used.
Those were the given memory resoures (Ignite 2.6):
[2018-08-16 15:07:49,961][INFO ][main][GridDiscoveryManager] Topology
snapshot [ver=1, servers=1, clients=0,
Denis Magda created IGNITE-9305:
---
Summary: Wrong off-heap size is reported for a node
Key: IGNITE-9305
URL: https://issues.apache.org/jira/browse/IGNITE-9305
Project: Ignite
Issue Type: Task
Dima,
"cache-less" means that SQL executed directly on SQL engine.
In previous version of Ignite we execute queries via cache:
ignite.cache("Some cache").sqlFieldsQuery("select ... from ..")
In current Ignite we can execute query directly without using cache as
"gateway".
And if we execute
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4511
---
Stuart, can you please move the ticket into PATCH_AVAILABLE state? You need
to click "Submit Patch" button in Jira.
D.
On Wed, Aug 15, 2018 at 10:22 AM, Stuart Macdonald
wrote:
> Here's the initial pull request for this issue, please review and let me
> know your feedback. I had to combine the
Evgeny, what is a "cache-less" SQL query?
D.
On Thu, Aug 16, 2018 at 6:36 AM, Evgenii Zhuravlev wrote:
> Hi Igniters,
>
> I've started to work on adding QueryDetailMetrics for cache-less SQL
> queries(issue https://issues.apache.org/jira/browse/IGNITE-6677) and found
> that it's required to
Ivan,
I implemented this issue, please review my changes.
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-729
On Thu, Aug 16, 2018 at 3:09 PM Ivan Rakov wrote:
> Thanks for your comments!
> I've created a ticket: https://issues.apache.org/jira/browse/IGNITE-9294
>
> Best Regards,
>
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4563
IGNITE-9294 Implement bounds for StandAloneWALIterator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Eduard Shangareev created IGNITE-9304:
-
Summary: AssertionError while updating ATOMIC cache while topology
changes
Key: IGNITE-9304
URL: https://issues.apache.org/jira/browse/IGNITE-9304
Project:
Aleksey Plekhanov created IGNITE-9303:
-
Summary: PageSnapshot can contain wrong pageId tag when not dirty
page is recycling
Key: IGNITE-9303
URL: https://issues.apache.org/jira/browse/IGNITE-9303
Hi Pavel,
Thank you for noticing and bringing it here. I've fixed TC failure.
Sincerely,
Dmitriy Pavlov
чт, 16 авг. 2018 г. в 0:10, Pavel Pereslegin :
> Hello Igniters.
>
> It seems that "idea/ignite_inspections.xml" should be excluded from
> "check-licenses" maven profile, because "_Licenses
Hi,
I've failed https://issues.apache.org/jira/browse/IGNITE-9301 and I'm
trying to disable test failure.
Help with .Net is really appreciated. I think it should not be a difficult
issue.
Sincerely,
Dmitriy Pavlov
чт, 16 авг. 2018 г. в 2:17, Vyacheslav Daradur :
> Hi, Alex, please have a
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4562
IGNITE-9302 Java Thin Clients TC configuration hangs because of no tiâ¦
â¦meout on tests
You can merge this pull request into a Git repository by running:
$ git pull
Eduard Shangareev created IGNITE-9302:
-
Summary: Java Thin Clients TC configuration hangs because of no
timeout on tests
Key: IGNITE-9302
URL: https://issues.apache.org/jira/browse/IGNITE-9302
Dmitriy Pavlov created IGNITE-9301:
--
Summary: Support method compute withNoResultCache in .Net
Key: IGNITE-9301
URL: https://issues.apache.org/jira/browse/IGNITE-9301
Project: Ignite
Issue
On Thu, Aug 16, 2018 at 8:39 AM, Paul Anderson wrote:
> Wonderful... I also have Netdata integration... (producing netdata charts
> straight from ignite) if you are interested...
>
> http://my-netdata.io
Yes, we are interested very much.
GitHub user zzzadruga opened a pull request:
https://github.com/apache/ignite/pull/4561
IGNITE-896 Configuration inconsistency
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zzzadruga/ignite IGNITE-896
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4518
---
Wonderful... I also have Netdata integration... (producing netdata charts
straight from ignite) if you are interested...
http://my-netdata.io
On Thu, 16 Aug 2018, 17:35 Dmitriy Pavlov, wrote:
> Hi Paul,
>
> I've added you to the list of contributors, so you can now assign the issue
> to
Hi Paul,
I've added you to the list of contributors, so you can now assign the issue
to yourself.
Being a contributor does not require you to participate any more than you
already do.
Sincerely,
Dmitriy Pavlov
чт, 16 авг. 2018 г. в 17:05, Paul Anderson :
> IGNITE-9298
>
> On Thu, 16 Aug 2018,
Hi Alex,
Thank you for referring spec. It really gives strict point how JCache
metrics should be counted.
So, I will start implementation of metrics for MVCC caches according to
spec and existing behavior.
As for improper "removals" calculation, I filed a ticket
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4554
---
Great idea!
Review is not only meant for the committers, but for everyone in the
community. Committers are only responsible for final reviews and merges.
D.
On Thu, Aug 16, 2018 at 7:29 AM, Dmitriy Pavlov
wrote:
> Hi Igniters,
>
> For a long time review queue in the community is quite long.
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4505
---
Ivan Pavlukhin created IGNITE-9300:
--
Summary: Removal count metric is calculated improperly for
transactional cache
Key: IGNITE-9300
URL: https://issues.apache.org/jira/browse/IGNITE-9300
Project:
Hi Igniters,
For a long time review queue in the community is quite long. Ticket count
is around 80-100 for last year. I would like to make the proposal, which
should help the community with this aspect. Being reviewer for some tickets
I found a number of tickets from new community members with
Pavel Tupitsyn created IGNITE-9299:
--
Summary: .NET: Support dependency injection for user-defined
classes that are instantiated by Ignite
Key: IGNITE-9299
URL: https://issues.apache.org/jira/browse/IGNITE-9299
IGNITE-9298
On Thu, 16 Aug 2018, 15:35 Nikolay Izhikov, wrote:
> Let's do it.
>
> Please, send a ticket number to this thread.
>
> В Чт, 16/08/2018 в 15:22 +0200, Paul Anderson пишет:
> > We needed here so I just did it... Very simple will raise a ticket and
> add
> > patch to it...
> >
> > On
Paul Anderson created IGNITE-9298:
-
Summary: control.sh does not support SSL
(org.apache.ignite.internal.commandline.CommandHandler)
Key: IGNITE-9298
URL: https://issues.apache.org/jira/browse/IGNITE-9298
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/4560
IGNITE-9297 Review ML examples javadocs as of release 2.6
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Hi Ivan,
Unfortunately, the review checklist does not work as well as it could. I
hope the situation will change in the nearest future, I think we should
come back to this idea and encourage contributors and reviewers to use the
list.
As for lambda's: some Igniters feel confident about it, and
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4484
---
Oleg Ignatenko created IGNITE-9297:
--
Summary: Review ML examples javadocs as of release 2.6
Key: IGNITE-9297
URL: https://issues.apache.org/jira/browse/IGNITE-9297
Project: Ignite
Issue
Sergey Kosarev created IGNITE-9296:
--
Summary: Stopping node by Failure Handler hangs up
Key: IGNITE-9296
URL: https://issues.apache.org/jira/browse/IGNITE-9296
Project: Ignite
Issue Type:
Hi Igniters,
I've started to work on adding QueryDetailMetrics for cache-less SQL
queries(issue https://issues.apache.org/jira/browse/IGNITE-6677) and found
that it's required to change API. I don't think that adding methods like
queryDetailMetrics, resetQueryDetailMetrics, as in IgniteCache to
Let's do it.
Please, send a ticket number to this thread.
В Чт, 16/08/2018 в 15:22 +0200, Paul Anderson пишет:
> We needed here so I just did it... Very simple will raise a ticket and add
> patch to it...
>
> On Thu, 16 Aug 2018, 15:21 Nikolay Izhikov, wrote:
>
> > Hello, Paul.
> >
> > Is
We needed here so I just did it... Very simple will raise a ticket and add
patch to it...
On Thu, 16 Aug 2018, 15:21 Nikolay Izhikov, wrote:
> Hello, Paul.
>
> Is there a ticket you trying to resolve?
> Yes, please, provide the patch, so community can take a look.
>
> В Чт, 16/08/2018 в 15:03
Hello, Paul.
Is there a ticket you trying to resolve?
Yes, please, provide the patch, so community can take a look.
В Чт, 16/08/2018 в 15:03 +0200, Paul Anderson пишет:
> org.apache.ignite.internal.commandline.CommandHandler (control.sh)
>
> Can I send you a diff rather than becoming a
org.apache.ignite.internal.commandline.CommandHandler (control.sh)
Can I send you a diff rather than becoming a contributer for the moment.
Thanks for your comments!
I've created a ticket: https://issues.apache.org/jira/browse/IGNITE-9294
Best Regards,
Ivan Rakov
On 15.08.2018 21:31, Dmitriy Setrakyan wrote:
Agree, this should be a great performance boost.
On Wed, Aug 15, 2018 at 10:17 AM, Dmitriy Pavlov
wrote:
Hi Ivan,
I
Ivan Rakov created IGNITE-9294:
--
Summary: StandaloneWalRecordsIterator: support iteration from
custom pointer
Key: IGNITE-9294
URL: https://issues.apache.org/jira/browse/IGNITE-9294
Project: Ignite
Hi Folks,
It seems it is a flaky failure, which unluckily failed 3 times in a row.
Sincerely,
Dmitriy Pavlov
чт, 16 авг. 2018 г. в 13:34, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
> *New test failure in
Filed a ticket: [1]
[1] - https://issues.apache.org/jira/browse/IGNITE-9293
Best Regards,
Igor
On Thu, Aug 16, 2018 at 3:28 AM Denis Magda wrote:
> Igor,
>
> I think it's reasonable to add the baseline topology APIs to C++. Can you
> plan this for the nearest releases?
>
> Pave, do you have
Igor Sapego created IGNITE-9293:
---
Summary: CPP: Add API to set baseline topology for C++
Key: IGNITE-9293
URL: https://issues.apache.org/jira/browse/IGNITE-9293
Project: Ignite
Issue Type:
Vladimir, yes I remember this discussion with Yuri. Of course I couldn't
estimate the changes to add new index type as you and thank you for your
consultation.
Maybe it's best approach to continue with my draft where it's implemented
via ML specific data structures over the cache.
2018-08-16
Ok, many thanks, will look at geospatial index
2018-08-16 14:10 GMT+06:00 Alexey Goncharuk :
> Alexey,
>
> I am not sure if it will be a proper fir for you, but I think it worth a
> try.
>
> Apache Ignite has an option to index geospatial data using third-party
> libraries (note that it is not
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
TcpCommunicationSpiSkipMessageSendTest.testClientSegmented
Dima,
By "out of question" I meant that 3rd party persistence should work out of
the box when IEP-22 is ready. No changes should be required there.
As far as persistence vs memory, most probably yes, there might be some
differences. Specifically, when data load starts and persistence is
enabled,
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4559
Ignite 9280
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-9280
Alternatively you can review and
GitHub user anton-vinogradov opened a pull request:
https://github.com/apache/ignite/pull/4558
Ignite 9053
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-9053
Alternatively you can review and apply these
Hi Igniters,
I feel monitoring will provide us with the necessary knowledge about how to
change.
I have no idea how region separation can help with performance. But it
could be an additional challenge for users to correctly configure separate
regions.
Sincerely,
Dmitriy Pavlov
чт, 16 авг. 2018
Ivan Pavlukhin created IGNITE-9292:
--
Summary: MVCC SQL: Race during updating TX log on near backup
Key: IGNITE-9292
URL: https://issues.apache.org/jira/browse/IGNITE-9292
Project: Ignite
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/4557
IGNITE-9278 Fix TensorFlow integration: Can't find free ports in range
You can merge this pull request into a Git repository by running:
$ git pull
On Thu, Aug 16, 2018 at 2:27 AM, Vladimir Ozerov
wrote:
> Dima,
>
> None database I know use separate regions for index pages due to the reason
> I expressed above. Instead, they split all pages into two groups - hot and
> cold. With certain rules on how to move pages inside and between these
>
Dima,
None database I know use separate regions for index pages due to the reason
I expressed above. Instead, they split all pages into two groups - hot and
cold. With certain rules on how to move pages inside and between these
groups. None of these algorithms are complex enough. In fact, they
Vladimir,
First of all, statements in Java 8 section [1] looks kind of prohibitive
for me. When a new contributor see words "preferred" and "avoided in most
cases" he most likely will not use such features (like I did). If a
statement is not prohibitive in practice it could be at least rephrased.
Sergey Kozlov created IGNITE-9291:
-
Summary: IgniteJdbcThinDriver with SSL doesn't work for sqlline on
Windows
Key: IGNITE-9291
URL: https://issues.apache.org/jira/browse/IGNITE-9291
Project: Ignite
On Thu, Aug 16, 2018 at 2:01 AM, Vladimir Ozerov
wrote:
> Hi Dima,
>
> Putting index pages in separate region is wrong approach, because data
> pages may be equally important on certain workloads, especially in
> heap-organized databases, such as Ignite
Never seen a use case where the data
Hi Dima,
Putting index pages in separate region is wrong approach, because data
pages may be equally important on certain workloads, especially in
heap-organized databases, such as Ignite.
At the moment we'd better focus on monitoring.to better understand usages
patterns. This would give us solid
On Thu, Aug 16, 2018 at 1:24 AM, Vladimir Ozerov
wrote:
> Hi Denis,
>
> This IEP is mostly about how we work with our own indexes and pages. So 3rd
> party DB is out of question.
>
Why? I think 3rd party DB will be supported automatically with CacheStore.
However, do we need to do something
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4556
IGNITE-9290: Make remove explicit locks async when node left.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Hi Denis,
This IEP is mostly about how we work with our own indexes and pages. So 3rd
party DB is out of question.
On Thu, Jun 21, 2018 at 10:38 PM Denis Magda wrote:
> Vladimir,
>
> As I see from the IEP, this data loading technique is supposed to be used
> for deployments with Ignite
Hi Ivan,
>From what I see we do not restrict contributors to use lambdas and streams.
Document states that plain collections and anonymous classes are
*preferred*. This is not obligatory requirement, and it seems reasonable to
me, because when developing complex projects at times it is better to
GitHub user udaykale opened a pull request:
https://github.com/apache/ignite/pull/4555
IGNITE-7054 S3 IP finder: support client side encryption
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/udaykale/ignite IGNITE-7054
Hi Alex,
>From what I see there is some interest to K-D indexes in SQL world.
Postgres has it. MySQL users asks about it from time to time, and usually
use some simpler spatial solutions ask MySQL lacks this index type. We
definitely may consider integrating it with SQL, but this would be big
Alexey,
I am not sure if it will be a proper fir for you, but I think it worth a
try.
Apache Ignite has an option to index geospatial data using third-party
libraries (note that it is not included in the default Ignite build, the
module is activated via the lgpl profile). The index is located in
Andrew Mashenkov created IGNITE-9290:
Summary: Make remove explicit locks async when node left.
Key: IGNITE-9290
URL: https://issues.apache.org/jira/browse/IGNITE-9290
Project: Ignite
Vladimir Ozerov created IGNITE-9289:
---
Summary: Document CPP thin client
Key: IGNITE-9289
URL: https://issues.apache.org/jira/browse/IGNITE-9289
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-9288:
---
Summary: Document how to start Ignite under Java 9
Key: IGNITE-9288
URL: https://issues.apache.org/jira/browse/IGNITE-9288
Project: Ignite
Issue Type:
Vladimir Ozerov created IGNITE-9287:
---
Summary: Document SQL best practices and known problems
Key: IGNITE-9287
URL: https://issues.apache.org/jira/browse/IGNITE-9287
Project: Ignite
Issue
GitHub user ekaterina-nbl opened a pull request:
https://github.com/apache/ignite/pull/4554
IGNITE-9258: NodeJS multiple clients fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nobitlost/ignite ignite-9258
Alternatively you
Dmitriy Shabalin created IGNITE-9286:
Summary: Redesign and Refactor UI
Key: IGNITE-9286
URL: https://issues.apache.org/jira/browse/IGNITE-9286
Project: Ignite
Issue Type: Improvement
GitHub user Dmitriyff opened a pull request:
https://github.com/apache/ignite/pull/4553
Ignite wc 585
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-wc-585
Alternatively you can review and apply
Ilya,
Can you please clarify what you mean by 'abandons cache store operations'?
Does it mean that a read-through/write-through op is omitted, but the
public API method returns without an error? If it is so, then this is a
bug. If a public API method finishes with an exception when read-through
Andrey, I agree that most likely this can be done in an async way. There
are some nuances, though, because if a node leaves during an ongoing
exchange, we should remove the locks in the context of the ongoing exchange
and not wait for the next exchange event.
I will take a look at your PR
77 matches
Mail list logo
