Hello, Prachi!
The section is a hand-written .rst-file, which contains links to some
content, generated from code with `sphinx-apidoc`.
All autogenerated content resides in `source` folder. For example, this
is an autogenerated page:
https://apache-ignite-binary-protocol-client.readthedocs.
Ilya Borisov created IGNITE-9476:
Summary: Web console: extract configuration-specific mixins from
mixins.pug
Key: IGNITE-9476
URL: https://issues.apache.org/jira/browse/IGNITE-9476
Project: Ignite
Hi Dmitry M,
Is the API Specification [1] section of the documentation auto-generated
from the code?
[1]
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/modules.html
On Mon, Jul 30, 2018 at 5:05 PM, Dmitriy Setrakyan
wrote:
> Now we are talking. A much better and more use
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/4690
Ignite 2.5.1 p12 notrace
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.5.1-p12-notrace
Alternatively you
We have needed to do a couple of simple bug fixes to ignite proper, where
there is no change to interfaces or internode communications. When we do
this, we end up with these choices:
- Coordinate client and server code bases so that they are in lock
step. Tedious with multiple clusters
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4687
---
GitHub user ololo3000 opened a pull request:
https://github.com/apache/ignite/pull/4689
IGNITE-8331 Add Decimal precision and scale constraint
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ololo3000/ignite IGNITE-8331
Alternat
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/4688
IGNITE-9475 Use proper task class name for the error message
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-94
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4687
Revert TOPIC_MONGO removal in "IGNITE-9361 Remove IgniteInternalCacheâ¦
â¦.isMongo*Cache() and other remnants."
This partially reverts commit de30a86e740067ed239602fb5dc28396144fd446.
You
Ivan Bessonov created IGNITE-9475:
-
Summary: Closures that has been created on client does not provide
real class name to TASK_* permissions
Key: IGNITE-9475
URL: https://issues.apache.org/jira/browse/IGNITE-9475
Pavel Vinokurov created IGNITE-9474:
---
Summary: Ignite does not eagerly remove expired cache entries
Key: IGNITE-9474
URL: https://issues.apache.org/jira/browse/IGNITE-9474
Project: Ignite
I
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4464
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4640
---
Rob Gibbon created IGNITE-9473:
--
Summary: InvalidPathException when localizing resources for Tez job
Key: IGNITE-9473
URL: https://issues.apache.org/jira/browse/IGNITE-9473
Project: Ignite
Issue
Hello!
1) It is really advised to run tests from IDEA (that's what absolute
majority of active contributors seem to be using), but you can also run it
with
mvn clean install -Dtest=SimpleClassNameOfTest -DfailIfNoTests=false
2) enable 'examples' profile and run ExampleNodeStartup class.
Regards,
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/4686
IGNITE-9472 Added permissions check on cluster activation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9472
Denis,
Discussion relocated to the issue.
Amir is working on implementation now.
ср, 5 сент. 2018 г. в 1:53, Denis Magda :
> Amir, Anton,
>
> How is dev/review process going? Is there any chance we get this capability
> into 2.7?
>
> --
> Denis
>
> On Mon, Jul 9, 2018 at 10:27 PM Amir Akhmedov
>
Ivan Bessonov created IGNITE-9472:
-
Summary: REST API has no permission checks for cluster
activation/deactivation
Key: IGNITE-9472
URL: https://issues.apache.org/jira/browse/IGNITE-9472
Project: Igni
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4685
IGNITE-4111
Fix for IGNITE-4111 Communication fails to send message if target node did
not finish join process
You can merge this pull request into a Git repository by running:
$ git pull
Hello!
Of course, this setting will be configurable.
Regards,
--
Ilya Kasnacheev
ср, 5 сент. 2018 г. в 3:21, Dmitriy Setrakyan :
> In my view, dictionary of 1024 bytes is not going to be nearly enough.
>
> On Tue, Sep 4, 2018 at 8:06 AM, Ilya Kasnacheev >
> wrote:
>
> > Hello!
> >
> > In cas
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4658
---
GitHub user deviljelly opened a pull request:
https://github.com/apache/ignite/pull/4684
IGNITE-9298
Adds support for SSL to CommandHandler (control.sh)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/deviljelly/ignite ignite-9298
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4682
---
Yes, I reviewed this ticket and it could be merged immediately.
5 сент. 2018 г. 9:30 AM пользователь "Ravil Galeyev"
написал:
> Hi team,
>
> Could @ybabak or someone, merge my PR
> https://github.com/apache/ignite/pull/4655
> for task https://issues.apache.org/jira/browse/IGNITE-9285
>
> @zales
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4650
---
Dmitriy Gladkikh created IGNITE-9471:
Summary: Failed to validate indexes by control.sh utility.
Key: IGNITE-9471
URL: https://issues.apache.org/jira/browse/IGNITE-9471
Project: Ignite
Is
Roman Kondakov created IGNITE-9470:
--
Summary: MVCC TX: Mvcc transactions should throw proper exception
when rolled back.
Key: IGNITE-9470
URL: https://issues.apache.org/jira/browse/IGNITE-9470
Projec
27 matches
Mail list logo
