Dear Devs, I starting experimenting with Ignite using java+jdbc over the
weekend. Really cool technology! In my tests, I ran into a couple issues that I
might have some time to help fix. For example:
(1) Ignite doesn't support auto incrementing keys so you can't use SQL
keywords like
Pavel Petroshenko created IGNITE-10230:
--
Summary: Putting collection of timestamps fails on python thin
client
Key: IGNITE-10230
URL: https://issues.apache.org/jira/browse/IGNITE-10230
Project:
Alexander Kalinin created IGNITE-10229:
--
Summary: Hide authentication dialog when agent/secure cluster is
disconnected.
Key: IGNITE-10229
URL: https://issues.apache.org/jira/browse/IGNITE-10229
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/4252
---
Hi Alex,
Thanks for the ideas! It will be useful.
However, from my side, Oracle like syntax looks excess. Will be good if
someone else say opinion opinion about syntax.
Igniters, what do you think which syntax of Ignite management via SQL will
be prefer?
пт, 9 нояб. 2018 г. в 0:37, Alex
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5327
---
ololo3000 opened a new pull request #67: IGNITE-10215 Inspections:Core failures
marked as critical
URL: https://github.com/apache/ignite-teamcity-bot/pull/67
This is an automated message from the Apache Git Service.
To
PetrovMikhail created IGNITE-10215:
--
Summary: [Tc Bot] Mark Inspections:Core failures as critical
Key: IGNITE-10215
URL: https://issues.apache.org/jira/browse/IGNITE-10215
Project: Ignite
Yury Gerzhedovich created IGNITE-10217:
--
Summary: Unwrap _KEY for secondary index
Key: IGNITE-10217
URL: https://issues.apache.org/jira/browse/IGNITE-10217
Project: Ignite
Issue Type:
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5363
IGNITE-10216: sort annotations according to inspection profile
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-10216
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/5364
Ignite 2.5.3.b1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.3.b1
Alternatively you can review and apply
Maxim Muzafarov created IGNITE-10216:
Summary: Sort annotations order according to inspection profile
Key: IGNITE-10216
URL: https://issues.apache.org/jira/browse/IGNITE-10216
Project: Ignite
Hello,Peter.
Welcome to Ignite community!
First of all, please, subscribe to dev-list.
Processes of code and doc contribution are described on wiki
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> which repo should I clone? It looks like there are two.
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5245
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5345
---
Yuri,
Do you have any ideas in mind?
On Mon, Nov 12, 2018 at 1:25 PM Юрий wrote:
> Hi Alex,
>
> Thanks for the ideas! It will be useful.
> However, from my side, Oracle like syntax looks excess. Will be good if
> someone else say opinion opinion about syntax.
>
> Igniters, what do you think
Andrew Mashenkov created IGNITE-10219:
-
Summary: MVCC: TX: Backup node update may fails after lost tx
rollback.
Key: IGNITE-10219
URL: https://issues.apache.org/jira/browse/IGNITE-10219
Project:
asfgit closed pull request #67: IGNITE-10215 Inspections:Core failures marked
as critical
URL: https://github.com/apache/ignite-teamcity-bot/pull/67
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
asfgit closed pull request #64: New Page for TC Bot: Long Running Tests Report
URL: https://github.com/apache/ignite-teamcity-bot/pull/64
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/5366
Ignite 9996-2.7
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-9996-2.7
Alternatively you can review and apply these
Sergey Kozlov created IGNITE-10222:
--
Summary: CPP Thin: Examples for operations with multiple keys and
values
Key: IGNITE-10222
URL: https://issues.apache.org/jira/browse/IGNITE-10222
Project:
Stanislav Lukyanov created IGNITE-10223:
---
Summary: Affinity methods should return List instead of Collection
Key: IGNITE-10223
URL: https://issues.apache.org/jira/browse/IGNITE-10223
Project:
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/5365
ignite-9858 do not initialize local addresses for the client node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Anton Dmitriev created IGNITE-10220:
---
Summary: ML: Merge TensorFlow IGFS and Ignite modules into one
module
Key: IGNITE-10220
URL: https://issues.apache.org/jira/browse/IGNITE-10220
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4991
---
Anton Dmitriev created IGNITE-10221:
---
Summary: ML: Fix all issues in "Add ability to start TensorFlow
server from Java API" PR
Key: IGNITE-10221
URL: https://issues.apache.org/jira/browse/IGNITE-10221
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/5350
---
Taras Ledkov created IGNITE-10224:
-
Summary: JDBC thin: the statement must be removed from statements
list when it is closed
Key: IGNITE-10224
URL: https://issues.apache.org/jira/browse/IGNITE-10224
Maxim Muzafarov created IGNITE-10227:
Summary: Update unused imports TC configuration of inspection
profile
Key: IGNITE-10227
URL: https://issues.apache.org/jira/browse/IGNITE-10227
Project:
Pavel Kovalenko created IGNITE-10226:
Summary: Partition may restore wrong MOVING state during crash
recovery
Key: IGNITE-10226
URL: https://issues.apache.org/jira/browse/IGNITE-10226
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5351
---
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5367
IGNITE-10227: fix unused imports configuration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-10227
Alternatively you
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/5363
---
Stanislav Lukyanov created IGNITE-10225:
---
Summary: Striped pool starvation check reports false-positive
warnings if a job starts right before the check
Key: IGNITE-10225
URL:
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5368
IGNITE-10226 Partition state recovery fix for 2.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14442
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5371
IGNITE- Logical recovery cleanup and refactoring
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-
Vyacheslav Koptilin created IGNITE-10228:
Summary: Start multiple caches in parallel may lead to the fact
that some of the caches won't be registered.
Key: IGNITE-10228
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4866
---
Sergey Antonov created IGNITE-10218:
---
Summary: Detecting lost partitions PME phase triggered twice on
coordinator
Key: IGNITE-10218
URL: https://issues.apache.org/jira/browse/IGNITE-10218
Project:
Vladimir,
I'd wish we could do that, but unfortunately, even VS 2017 does not
support all C++11 (and even C++03) features [1]. So, maybe we should
also speak about dropping support of old VS and moving to at least VS 2012.
You can find the benefits of this at [2]. For example, this will give us
Hi Jörn,
Agree, it is also my understanding that after we migrate part of the tests
that still use JUnit 3 (https://issues.apache.org/jira/browse/IGNITE-10173),
upgrade to next version is going to be easy and low risk.
With regards to asserting exceptions I think you have a good point here, I
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/5369
IGNITE-10174 migrate examples tests from Junit 3 to 4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10174
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5370
GG-14435 condition was changed in assertion.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14435
Hi Ivan,
I am currently testing approach you used in pull/5354 in the "pilot"
sub-task with examples tests (IGNITE-10174).
So far it looks more and more like the way to go. The most promising thing I
observed is that after I changed classes in our test framework the way you
did, execution of
Igniters,
Below is a proposed design for thin client SQL management and monitoring to
cancel a queries.
1) Ignite expose system SQL view with name *running_queries*
proposed columns: *node_id, query_id, sql, schema_name, connection_id,
duration*.
node_id - initial node of request
query_id -
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/5372
Tdr 127 ag master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite tdr-127-ag-master
Alternatively you can review and
46 matches
Mail list logo
