Hello, Dmitry.
I have some experience with ContinuousQuery codebase so ca take care of
this ticket. Can you provide it ID?
В Вт, 26/12/2017 в 18:10 +0300, Dmitry Karachentsev пишет:
> Hi Nikolay,
>
> I think it may be useful too. Will try to describe possible API in a
> ticket.
>
> Thanks!
> -
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/3307
IGNITE-7323: Update Storm dependencies to 1.1.1.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite IGNITE-7323
Alternatively you
Roman Shtykh created IGNITE-7323:
Summary: Up
Key: IGNITE-7323
URL: https://issues.apache.org/jira/browse/IGNITE-7323
Project: Ignite
Issue Type: Bug
Reporter: Roman Shtykh
Pavel,
I have 2 records in my cache, and when I run an example for
OP_QUERY_SQL=2002 with cursor page size 1, I get the following result
(expected)
len: 83
resReqId: 1
status code: 0
cursorId: 1
rowCount: 1
moreResults: true
Then, I run the OP_QUERY_SQL_CURSOR_GET_PAGE = 2003, using the followin
Hello Jason,
Granted you the required permissions. Thanks for the contribution!
Igor, could you validate the changes?
—
Denis
> On Dec 26, 2017, at 5:53 PM, Jason Man wrote:
>
> Hello,
>
> Please grant me access to assign myself Ignite issues. I want to fix one
> of Ignite's issue IGNITE-68
On Wed, Dec 27, 2017 at 8:05 AM, Pavel Tupitsyn
wrote:
> Yep, base64 is just an example.
> We need some kind of urlencode, but tailored for file names, so that
> names remain readable.
>
> To avoid uppercase/lowercase collisions on Windows, we can restrict allowed
> characters to lowercase Englis
Pavel,
I am trying to come up with an example for OP_PUT_BINARY_TYPE = 3003.
However, few things are not clear to me from the wiki doc -
1. In BinaryField, What is Field id?
2. If there is no enum, what should I put for 'Enum values'?
3. What is Schema?
-P
Igniters
Use cache name for file and directory names on a file system is bad idea.
In that case we should keep in mind many limitiations vary FS.
Why do not use mapping cache name to an identifier tolerated to FS lacks?
On Wed, Dec 27, 2017 at 7:05 PM, Pavel Tupitsyn
wrote:
> Yep, base64 is jus
Ticket was assigned to me until the patch available state has been reached.
Till now no one committer take responsibility to review and merge the PR.
2017-12-26 21:08 GMT+07:00 Dmitriy Setrakyan :
> Here is the link to the ticket:
> https://issues.apache.org/jira/browse/IGNITE-7135
>
> For some
Artem Malykh created IGNITE-7322:
Summary: Distributed MLP training
Key: IGNITE-7322
URL: https://issues.apache.org/jira/browse/IGNITE-7322
Project: Ignite
Issue Type: Sub-task
Affects Ve
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3306
ignite-6736 Unsafe.monitorEnter/Exit usages are removed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-2.4-java8
Yep, base64 is just an example.
We need some kind of urlencode, but tailored for file names, so that
names remain readable.
To avoid uppercase/lowercase collisions on Windows, we can restrict allowed
characters
to lowercase English letters and numbers, - and _, and escape everything
else in some w
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3305
ignite-6745 URLClassLoader.getURLs() usages are removed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-6745
Alter
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/3304
IGNITE-7259
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7259
Alternatively you can review and apply th
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/3303
IGNITE-7205: Dataset API
1. Changed Labeled Dataset
2. Added Dataset and DatasetRow classes
3. Moved a few methods to Normalizer and LabeledDatasetLoader
4. Changed examples and tes
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/3302
IGNITE-7312: Made use of java.util.Base64 for base64 encoding.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite
On Wed, Dec 27, 2017 at 6:25 AM, Vladimir Ozerov
wrote:
> Having different policies for persistent and non-persistent caches sounds
> like a bad idea for me, because there could be troubles should user try to
> switch to persistent mode. It would require code changes.
>
> Can we just escape all n
Having different policies for persistent and non-persistent caches sounds
like a bad idea for me, because there could be troubles should user try to
switch to persistent mode. It would require code changes.
Can we just escape all non-latin symbols (e.g. using base64), while leaving
the rest as is?
On Wed, Dec 27, 2017 at 3:42 AM, Pavel Tupitsyn
wrote:
> Agree with Stan and Vladimir.
> We should not impose any restrictions on cache names, some users may have
> issues with that.
>
> Using cache names as file names is internal implementation detail.
> We can use cache id or some kind of encod
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3301
Ignite 7217
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7217
Alternatively you can review and apply these c
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/3300
---
Github user slukyano closed the pull request at:
https://github.com/apache/ignite/pull/3268
---
Github user gvvinblade closed the pull request at:
https://github.com/apache/ignite/pull/3299
---
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3300
IGNITE-7321 mvcc enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-7321-mvcc-enabled
Alternatively you
Also, considering case-insensitivity issue, we need to choose
some encoding that only uses upper or lower case letters in
encoding result.
By the way, such encoding will resolve cache name clashes
due to case-insensitivity issue.
Best Regards,
Igor
On Wed, Dec 27, 2017 at 4:18 PM, Igor Sapego w
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/3299
IGNITE-7321
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7321
Alternatively you can review and apply these
I personally like a Pavel's suggestion - base64 encoding seems like
a good solution, while string hashes will arise a collision issue.
Best Regards,
Igor
On Wed, Dec 27, 2017 at 3:29 PM, Petr Ivanov wrote:
> Special characters banning seems to be exclusive way and cannot be
> controlled in futu
Special characters banning seems to be exclusive way and cannot be controlled
in future if new symbols arise.
Maybe better solution will be choosing the array of permitted symbols for
caches names (i.e. [a-zA-Z0-9_-])?
Also +1 for using abstract hash string for directories names.
> On 27 Dec
We can – by mapping a cache name to some (safe) string to be used as a
directory name, say via Base64 as Pavel has suggested.
However, I think that banning certain characters might be reasonable.
Some characters might be considered reserved (e.g. slashes, colon, asterisk,
etc) to be used later,
GitHub user dolphin1414 opened a pull request:
https://github.com/apache/ignite/pull/3298
IGNITE-6022: Implemented native batch execution support for DML statements.
Implemented native batch execution support for DML statements.
You can merge this pull request into a Git repository
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/3297
IGNITE-6783: Create common mechanism for group training.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6783
Vladimir Ozerov created IGNITE-7321:
---
Summary: DML operation hangs in case exception is thrown from DHT
enlist future
Key: IGNITE-7321
URL: https://issues.apache.org/jira/browse/IGNITE-7321
Project:
Agree with Stan and Vladimir.
We should not impose any restrictions on cache names, some users may have
issues with that.
Using cache names as file names is internal implementation detail.
We can use cache id or some kind of encoding (base64, etc) to avoid file
system issues.
Thanks,
Pavel
On We
That’s interesting, thanks.
So, do you think the locale-specific file separators should be banned as well?
Handling all kinds of cases like this might be complicated.
I’d rather use something else if the cache name is not a valid file name, a
hash of the cache name.
This way all corner cases can
Cache name appears to me purely logical entity. Can we simply store cache
ID in file system paths without adding any restrictions to cache names?
On Wed, Dec 27, 2017 at 2:26 PM, Stanislav Lukyanov
wrote:
> Well, that’s my question too :)
> Do we have any compatibility guidelines or other docume
Well, that’s my question too :)
Do we have any compatibility guidelines or other documents on what can or
cannot be in a minor/major release?
Also, it might be helpful to add an environment variable (like
IGNITE_DISABLE_CACHE_NAME_RESTRICTIONS) to restore the old behavior, just in
case.
Thanks
GitHub user bbarin opened a pull request:
https://github.com/apache/ignite/pull/3296
IGNITE-7304
I didn't figured out how to write integration tests without providing the
AWS credentials.
You can merge this pull request into a Git repository by running:
$ git pull https://gith
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3295
IGNITE-7293
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7293
Alternatively you can review and apply these
Hi, Igniters!
I’m working on an implementation of 3rd party persistence solution.
The solution is annotated by CacheLocalStore annotation.
As far as I know, CacheLocalStore annotation means that server node
persists its own primary and backup partitions (please correct me if
I’m wrong).
How abo
Hi, looks like there is no much profit when PDS throttling is enabled
and tuned according to an article [1].
I’ve benchmarked the solutions with ‘put’ operation for 3 hours via
Ignite Yardstick. I see quite similar results with the write-heavy
pattern. Most time PDS works ~10% faster. Only one thi
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/3294
IGNITE-7302
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7302
Alternatively you can review and apply th
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/3293
IGNITE-7280
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7280
Alternatively you can review and apply th
Alexander Kalinin created IGNITE-7320:
-
Summary: Multilevel header in admin panel looks wierd in Safari
and Edge
Key: IGNITE-7320
URL: https://issues.apache.org/jira/browse/IGNITE-7320
Project: Ig
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3287
---
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/3292
IGNITE-6923 Optimize metrics calculation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite IGNITE-6923
Alternativel
45 matches
Mail list logo