Github user DmitriyGovorukhin closed the pull request at:
https://github.com/apache/ignite/pull/3170
---
Alexey Popov created IGNITE-7153:
Summary: Redis: BufferUnderflowException at
GridRedisProtocolParser.readBulkStr for values > 8kb
Key: IGNITE-7153
URL: https://issues.apache.org/jira/browse/IGNITE-7153
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/3179
IGNITE-7052 S3 IP finder: add an ability to provide endpoint address
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Yury Babak created IGNITE-7149:
--
Summary: Gradient boosting for decision tree
Key: IGNITE-7149
URL: https://issues.apache.org/jira/browse/IGNITE-7149
Project: Ignite
Issue Type: New Feature
Alexandr Kuramshin created IGNITE-7152:
--
Summary: Failure detection timeout don't work on permanent send
message errors causing infinite loop
Key: IGNITE-7152
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3121
---
Pavel Tupitsyn created IGNITE-7154:
--
Summary: .NET: Thin client: Async queries
Key: IGNITE-7154
URL: https://issues.apache.org/jira/browse/IGNITE-7154
Project: Ignite
Issue Type:
GitHub user gg-shq opened a pull request:
https://github.com/apache/ignite/pull/3183
IGNITE-6915: Fixed b+tree index names for non-binary marshaller case...
⦠Added more diagnostics to QueryXxxAccessor exceptions.
You can merge this pull request into a Git repository by running:
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/3178
IGNITE-7135 IgniteCluster.startNodes() returns successful
ClusterStartNodeResult even though the remote process fails.
Fix windows startup scripts. Add startNodes() Windows support through
Sergey Chugunov created IGNITE-7148:
---
Summary: BinaryMetadata file store should check each file whether
it is corrupted (zero length)
Key: IGNITE-7148
URL: https://issues.apache.org/jira/browse/IGNITE-7148
Yury Babak created IGNITE-7150:
--
Summary: Gradient boosting for lin regression
Key: IGNITE-7150
URL: https://issues.apache.org/jira/browse/IGNITE-7150
Project: Ignite
Issue Type: New Feature
Dmitriy Shabalin created IGNITE-7147:
Summary: Implemente connected clusters component
Key: IGNITE-7147
URL: https://issues.apache.org/jira/browse/IGNITE-7147
Project: Ignite
Issue Type:
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/3180
IGNITE-6224: Waiting TX completion on node stop.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-6224
Igor Sapego created IGNITE-7151:
---
Summary: CPP: Get rid of code duplication in JNI library
Key: IGNITE-7151
URL: https://issues.apache.org/jira/browse/IGNITE-7151
Project: Ignite
Issue Type:
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/3181
Ignite 6902
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6902
Alternatively you can review and
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/3184
IGNITE-6729: Removed obsolete reflection-based workaround
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3185
IGNITE-4750: support GROUP_CONCAT for collocated queries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Thank you, I will have a try
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/3187
IGNITE-7109 .NET: Thin client: Async cache operations
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7109
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/3188
Ignite 2.4.1 p3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p3
Alternatively you can review
thank you very much.
as I had the settings as below, ignite should have enough information to
figure out key and value type,right?
@QuerySqlField(index = true)
private String appId;
@QuerySqlField(index = true)
private String uid;
--
Sent from:
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/3189
Ignite 7053
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7053
Alternatively you can review and apply these
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3186
Ignite 1.8.16
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.16
Alternatively you can review and apply
Not sure I understand the question. @QuerySqlField annotates a particular
field that can be in either key and value object. To specify which objects
are stored in cache and therefore which classes Ignite should scan for
these annotations, you should use setIndexedTypes.
Please refer to
24 matches
Mail list logo
