Stepan Pilschikov created IGNITE-9908:
-
Summary: thin python: Can't use client with windows
Key: IGNITE-9908
URL: https://issues.apache.org/jira/browse/IGNITE-9908
Project: Ignite
Issue T
Dmitry,
I've trying to use python thin client with Ignite 2.7 it dosn't work
Please help to investigate
Problem reproduced on several others machines
Issue:
https://issues.apache.org/jira/browse/IGNITE-9908
вт, 16 окт. 2018 г. в 4:36, Dmitry Melnichuk :
> Igor,
>
> I do not have access to edit
Hello, Igniters.
9 tickets to go!
Alexey Goncharuk - IGNITE-9784
Dmitriy Govorukhin - IGNITE-9898
Andrey Kuznetsov - IGNITE-9737, IGNITE-9710
Taras Ledkov - IGNITE-9882
Petr Ivanov - IGNITE-9852
Ivan Pavlukhin - IGNITE-5935
Roman Kondakov - IGNITE-9663
Alexey Stelmak - IGNITE-9776
В Вт
Hi NIkolay,
Thank you for keeping everybody focused! Regarding to my ticket IGNITE-5935.
It is in final stage now. Tests look good. I believe that it will be merged
in couple of days (at most).
ср, 17 окт. 2018 г. в 11:39, Nikolay Izhikov :
> Hello, Igniters.
>
> 9 tickets to go!
>
> Alexey Gonc
Anton Kalashnikov created IGNITE-9909:
-
Summary: Merge FsyncWalManager and WalManager
Key: IGNITE-9909
URL: https://issues.apache.org/jira/browse/IGNITE-9909
Project: Ignite
Issue Type: I
+ 1
I dislike the current list of abbreviations. It gives me a pain to support
code with unclear variables naming, also I agree that we should avoid crazy
Java camel long naming like
FactoryBuildingCrazyAffinityCallerForComibingInSpace but instead that we
make shorter clear concepts like /counter/,
I'm sorry, but the IgniteDataset can not be used like a basic term, due to
it's ML specific term and also we have a few kind of datasets (that are not
equivalents of IgniteCache/Space and etc) like IgniteDataset,
PartitionBasedDataset, LocalCachedDataset and so on.
Of course, we could find a datas
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/5009
IGNITE-9877 .NET: Fix AmbiguousMatchException in LINQ under .NET Core 2.1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ig
>From my perspective, the main goal is to make easy the explanation what is
Ignite on conferences, marketing deals, in papers, in documentation. And the
/cache/ term really reduces the area of Ignite usage in users minds.
I don't support the critical changes in code base, but I support all changes
Hi Igniters,
I'd like to include IGNITE-9877 in 2.7, can we do that?
The fix is ready, I'm waiting for TC run.
Pavel
On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван wrote:
> Hi NIkolay,
>
> Thank you for keeping everybody focused! Regarding to my ticket
> IGNITE-5935.
> It is in final stage now
+ 1
But, I think that we must leave abbreviations for common words with single
meaning. For example, group -> grp, transaction -> tx, context -> ctx.
ср, 17 окт. 2018 г. в 12:46, Alexey Zinoviev :
> + 1
> I dislike the current list of abbreviations. It gives me a pain to support
> code with uncl
Hello, Pavel.
Is it a blocker?
В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет:
> Hi Igniters,
>
> I'd like to include IGNITE-9877 in 2.7, can we do that?
> The fix is ready, I'm waiting for TC run.
>
> Pavel
>
> On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван wrote:
>
> > Hi NIkolay,
>
+1
I asked a few guys, who use Ignite with Spark integration and (sometimes)
IGFS, nobody use it via Hadoop Accelerator build
ср, 17 окт. 2018 г. в 4:12, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> +1 from me. Hadoop Accelerator build is confusing and doesn't provide any
> value.
>
>
Nikolay,
It completely breaks a major feature under certain conditions. I would
consider it a blocker.
On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov wrote:
> Hello, Pavel.
>
> Is it a blocker?
>
> В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет:
> > Hi Igniters,
> >
> > I'd like to inclu
I'm not an ML expert, so 'dataset' term just reminds me of various client
drivers to access tables from RDBM servers. For me, the only common trait
of all kinds of Ignite caches is their asociativity. So if we rename them
I'd suggest something like KVStore.
ср, 17 окт. 2018 г. в 12:56, Alexey Zino
Pavel.
Ok, I agree to include this ticket into 2.7
Let's do it.
В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет:
> Nikolay,
>
> It completely breaks a major feature under certain conditions. I would
> consider it a blocker.
>
> On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov wrote:
>
> >
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4800
---
Well, the obvious term for me is a "Store" or "MemoryStore", as we already
have persistence store.
Best Regards,
Igor
On Wed, Oct 17, 2018 at 1:19 PM Andrey Kuznetsov wrote:
> I'm not an ML expert, so 'dataset' term just reminds me of various client
> drivers to access tables from RDBM servers
+ 1 from me to make abbreviations optional.
On Wed, Oct 17, 2018 at 1:00 PM Sergey Antonov
wrote:
> + 1
>
> But, I think that we must leave abbreviations for common words with single
> meaning. For example, group -> grp, transaction -> tx, context -> ctx.
>
> ср, 17 окт. 2018 г. в 12:46, Alexey
Unfortunately, we already use the word *"store"* for many other concepts,
like CacheStore and PageStore. I'd prefer to avoid giving it one more
meaning.
As already mentioned, *"dataset"* has special meaning for ML folks.
*"Bucket" *might give wrong association with bucket in a hash table.
On Wed
As I see, many people agree that the term *"cache"* is outdated, but
consider these changes too disruptive.
For me, keeping terminology up-to-date is important part of project
development. If we change some of our core terms with more relevant ones,
it indeed might cause confusion for current user
Aleksey Zinoviev created IGNITE-9910:
Summary: [ML] Move the static copy-pasted datasets from examples
to special Util class
Key: IGNITE-9910
URL: https://issues.apache.org/jira/browse/IGNITE-9910
Igor Seliverstov created IGNITE-9911:
Summary:
CacheMvccSelectForUpdateQueryAbstractTest#testSelectForUpdateAfterAbortedTx
periodically hangs
Key: IGNITE-9911
URL: https://issues.apache.org/jira/browse/IGNITE
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4996
---
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/5010
IGNITE-5565 replace Cron4J with Spring task scheduler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5565-2
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5002
---
Peter Ivanov created IGNITE-9912:
Summary: Improve Javadoc suite
Key: IGNITE-9912
URL: https://issues.apache.org/jira/browse/IGNITE-9912
Project: Ignite
Issue Type: Improvement
Re
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/5011
IGNITE-9899 Fix processing of TX cache backups by continuous queries.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
Ivan Rakov created IGNITE-9913:
--
Summary: Prevent data updates blocking in case of backup BLT
server node leave
Key: IGNITE-9913
URL: https://issues.apache.org/jira/browse/IGNITE-9913
Project: Ignite
+1 to
> leave abbreviations for common words with single meaning. For example,
group -> grp, transaction -> tx, context -> ctx.
And optional for the multi-words.
ср, 17 окт. 2018 г. в 14:54, Ilya Lantukh :
> + 1 from me to make abbreviations optional.
>
> On Wed, Oct 17, 2018 at 1:00 PM Sergey A
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4983
---
Andrey Aleksandrov created IGNITE-9914:
--
Summary: SubjectId for TaskEvents is incorrect for remote clients
Key: IGNITE-9914
URL: https://issues.apache.org/jira/browse/IGNITE-9914
Project: Ignite
Ivan Bessonov created IGNITE-9916:
-
Summary: Do not block SQL operations during exchange.
Key: IGNITE-9916
URL: https://issues.apache.org/jira/browse/IGNITE-9916
Project: Ignite
Issue Type: S
Ivan Bessonov created IGNITE-9915:
-
Summary: Do not block get/getAll during baseline node stopping.
Key: IGNITE-9915
URL: https://issues.apache.org/jira/browse/IGNITE-9915
Project: Ignite
Iss
Ivan Bessonov created IGNITE-9917:
-
Summary: Write proper tests for start/stop client.
Key: IGNITE-9917
URL: https://issues.apache.org/jira/browse/IGNITE-9917
Project: Ignite
Issue Type: Sub-
Sergey Kozlov created IGNITE-9918:
-
Summary: Default configuration missed
Key: IGNITE-9918
URL: https://issues.apache.org/jira/browse/IGNITE-9918
Project: Ignite
Issue Type: Bug
Com
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5003
---
Vladimir Ozerov created IGNITE-9919:
---
Summary:
IgniteHadoopFileSystemAbstractSelfTest.testRenameIfSrcPathIsAlreadyBeingOpenedToRead
fails
Key: IGNITE-9919
URL: https://issues.apache.org/jira/browse/IGNITE-9919
Vladimir Ozerov created IGNITE-9920:
---
Summary: Hadoop: native dependencies are not resolved properly
Key: IGNITE-9920
URL: https://issues.apache.org/jira/browse/IGNITE-9920
Project: Ignite
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/5009
---
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/5012
check PDS 2 (indexing) exit code 130
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite PDS-2-indexing-130-code
Alternatively yo
Thank you. Fix has been merged to master and cherry-picked to ignite-2.7.
On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov wrote:
> Pavel.
>
> Ok, I agree to include this ticket into 2.7
> Let's do it.
>
> В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет:
> > Nikolay,
> >
> > It completely br
JFYI
IGNITE-9737 and IGNITE-9710 are merged to release branch.
On Wed, Oct 17, 2018 at 5:41 PM Pavel Tupitsyn wrote:
>
> Thank you. Fix has been merged to master and cherry-picked to ignite-2.7.
>
> On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov wrote:
>
> > Pavel.
> >
> > Ok, I agree to includ
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/5013
IGNITE-9909 Extract file handle from WAL manager
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9909
Alternativ
Igor Sapego created IGNITE-9922:
---
Summary: Python thin: python directory should be included in
binary release
Key: IGNITE-9922
URL: https://issues.apache.org/jira/browse/IGNITE-9922
Project: Ignite
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/5014
IGNITE-9918 Default configuration missed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9918
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4619
---
Maxim Muzafarov created IGNITE-9923:
---
Summary: Fix unused imprts according to inspections profile
Key: IGNITE-9923
URL: https://issues.apache.org/jira/browse/IGNITE-9923
Project: Ignite
Iss
Hello,
Seems that SQL engine always deserialize whole objects instead of using just
SQL enabled fields (annotated with @QuerySqlField). This may have a huge
impact on Ignite heap usage and GC overhead as well.
For example, we have a cache holding big objects but with only two sql query
fields wh
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/5015
IGNITE-9922 Python thin: python directory should be included in binarâ¦
â¦y release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/a
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5016
IGNITE-9420 Logical recovery before PME
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9420
Alternatively you ca
Hi Igor,
We never deserialize values during query execution. Instead, we copy the
row to heap and extract fields as needed. In general case it is impossible
to avoid reading the whole row because we do not know whether this is
COUNT(*) or COUNT(*) WHERE or COUNT() WHERE
.
We do handle plain COUNT
Moving to dev forum...
Hello,
Seems that SQL engine always deserialize whole objects instead of using just
SQL enabled fields (annotated with @QuerySqlField). This may have a huge
impact on Ignite heap usage and GC overhead as well.
For example, we have a cache holding big objects but with onl
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5015
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4936
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4914
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4962
---
GitHub user dmelnichuk opened a pull request:
https://github.com/apache/ignite/pull/5017
Ignite 9908
Ensure compatibility with Windows (setup and 8-byte data type).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nobitlost/ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4975
---
Vladimir,
Thanks for explanation... that’s true - ignite never deserialize values
during query execution. The point here is why copying fields to heap that
sql engine could not use (not annotated as QuerySqlField)?
SQL count is a perfect example where you can benefit (heap space and gc)
copying on
Stepan,
Sadly, it was a C `long` data type size mismatch between Windows and
other OSes. I investigated this issue and offered a pull request.
https://github.com/apache/ignite/pull/5017
On 10/17/18 6:29 PM, Stepan Pilschikov wrote:
Dmitry,
I've trying to use python thin client with Ignite 2
Dmitry,
Great, now client works properly on all OS
Thanks
I hope PR will be merged soon
Igor, can please help with that?
ср, 17 окт. 2018 г. в 20:48, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan,
>
> Sadly, it was a C `long` data type size mismatch between Windows and
> other O
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5018
IGNITE-9663: Data node failure can cause TX hanging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9663
Alte
I do not understand - why are we copying values on-heap? If we must copy
something, why not copy rows into some off-heap space and read what we have
from there? At least this way we will not burden the JVM with extra GC
pressure.
D.
On Wed, Oct 17, 2018 at 10:33 AM Igor Tanackovic
wrote:
> Vlad
If dataset cannot be used, can we still consider "IgniteData"?
D.
On Wed, Oct 17, 2018 at 5:06 AM Ilya Lantukh wrote:
> As I see, many people agree that the term *"cache"* is outdated, but
> consider these changes too disruptive.
>
> For me, keeping terminology up-to-date is important part of p
Dmitriy,
Correct me if I’m wrong, but the concept is to store everything off heap -
which is perfectly fine :). So, the question is how SQL engine actually works.
Analyzing profiler object generation and sizes on heap, I’ve learned that for
each query entire rows in question are copied on heap
I've been calling everything "tables" instead of "caches" for a while. The
main reason is the maturity of our SQL engine - seeing more SQL users and
deployments which talk "tables" language.
On Wed, Oct 17, 2018 at 3:55 PM Dmitriy Setrakyan
wrote:
> If dataset cannot be used, can we still consi
On Wed, Oct 17, 2018 at 4:58 PM Denis Magda wrote:
> I've been calling everything "tables" instead of "caches" for a while. The
> main reason is the maturity of our SQL engine - seeing more SQL users and
> deployments which talk "tables" language.
>
>
I think "IgniteTable" only implies SQL, not k
Mikhail Cherkasov created IGNITE-9924:
-
Summary: Rename "allow non-collacated joins" to allow distributed
joins
Key: IGNITE-9924
URL: https://issues.apache.org/jira/browse/IGNITE-9924
Project: Ign
Key-value calls are just primary key based calls. From a user perspective,
it's the same as "SELECT * FROM table WHERE primary_idx = X", just
different API.
--
Denis
On Wed, Oct 17, 2018 at 5:04 PM Dmitriy Setrakyan
wrote:
> On Wed, Oct 17, 2018 at 4:58 PM Denis Magda wrote:
>
> > I've been ca
Mikhail Cherkasov created IGNITE-9925:
-
Summary: Validate QueryEntites on cache creation
Key: IGNITE-9925
URL: https://issues.apache.org/jira/browse/IGNITE-9925
Project: Ignite
Issue Type
No objections from my side.
--
Denis
On Tue, Oct 16, 2018 at 4:45 PM Dmitriy Setrakyan
wrote:
> Igniters,
>
> I would like to suggest dropping the hadoop accelerator distribution of
> Apache Ignite. Note, that it does not mean dropping any features. We are
> still going to support IGFS, in-mem
Or we could extend our SQL commands by "GET BY KEY = X" and "PUT (x1, x2,
x3) BY KEY = X" and the IgniteTable could be correct.
Agree with Denis that each table in the 3rd normal form is like key-value
store. Key-value operations are only subset of rich SQL commands.
The problem with IgniteData th
Well, I never thought about term “table” as a replacement for “cache”, but
it appears to be good candidate.
This is used by many some major vendors whose underlying storage is indeed
a kind of key-value data structure. Most well-known example is MySQL with
its MyISAM engine. Table can be used for
GitHub user nva opened a pull request:
https://github.com/apache/ignite/pull/5019
IGNITE-9308 Added baseline topology command to REST API.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9308
Altern
75 matches
Mail list logo
