Igor Sapego created IGNITE-13737:
Summary: Move PHP thin client to a separate git repo
Key: IGNITE-13737
URL: https://issues.apache.org/jira/browse/IGNITE-13737
Project: Ignite
Issue Type
Alexander Kovalev created IGNITE-12762:
--
Summary: PHP: Thin client: Transactions
Key: IGNITE-12762
URL: https://issues.apache.org/jira/browse/IGNITE-12762
Project: Ignite
Issue Type
Igor Sapego created IGNITE-11596:
Summary: PHP thin client UUID marshalling is wrong
Key: IGNITE-11596
URL: https://issues.apache.org/jira/browse/IGNITE-11596
Project: Ignite
Issue Type: Bug
oblem with
>>> DATA and TIMESTAMP data types
>>> I'ts appear when you trying to use DATA or TIMESTAMP as cache key
>>>
>>> All description in ticket:
>>> https://issues.apache.org/jira/browse/IGNITE-9951
>>>
>>> Can you help with that,
; I'ts appear when you trying to use DATA or TIMESTAMP as cache key
>>
>> All description in ticket:
>> https://issues.apache.org/jira/browse/IGNITE-9951
>>
>> Can you help with that, please?
>>
>> чт, 11 окт. 2018 г. в 16:02, Igor Sapego :
>>
>>
nd TIMESTAMP data types
> I'ts appear when you trying to use DATA or TIMESTAMP as cache key
>
> All description in ticket:
> https://issues.apache.org/jira/browse/IGNITE-9951
>
> Can you help with that, please?
>
> чт, 11 окт. 2018 г. в 16:02, Igor Sapego :
>
> >
lease?
чт, 11 окт. 2018 г. в 16:02, Igor Sapego :
> Alexey,
>
> Since PHP thin client is now in master, can you please add it to our
> "Thin clients features" wiki page, so we can track the feature parity
> of our clients?
>
> [1] -
> https://cwiki.apache.org/con
Alexey,
Since PHP thin client is now in master, can you please add it to our
"Thin clients features" wiki page, so we can track the feature parity
of our clients?
[1] -
https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features
Best Regards,
Igor
On Wed, Oct 10, 2018
I am not sure there is an answer. This is just how we handled it before.
IMO both approaches works fine. BTW, I already merged Vyacheslav's PR
several hours ago.
On Wed, Oct 10, 2018 at 1:24 PM Igor Sapego wrote:
> Vyacheslav,
>
> In this case, we should do the same with all existing doxygen
> f
Vyacheslav,
In this case, we should do the same with all existing doxygen
files, not only this one (see files with .dxg extension)
Vova, Pavel,
Were there historically any reasons to exclude doxygen files
from check instead of adding a license header?
Best Regards,
Igor
On Tue, Oct 9, 2018 at
Great work guys, thanks!
I've noticed TC fails in the build plan "Licenses Headers" which Igor
have fixed already by excluding Doxyfile from checking.
I've filled a ticket [1] and I'd suggest fixing the test in another
way by adding the license header to Doxyfile.
Igor, please, have a look at pr
As the seem to be everything OK with the code and tests and
no one had any comment for quite some time, I've merged the
PHP to Ignite's master.
Great job, guys!
Best Regards,
Igor
On Wed, Sep 19, 2018 at 1:00 AM Prachi Garg wrote:
> Hi Stephan, Alexey
>
> That's exactly what readme.io contai
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4649
---
Igor Sapego created IGNITE-9823:
---
Summary: Create TeamCity suite for PHP thin client
Key: IGNITE-9823
URL: https://issues.apache.org/jira/browse/IGNITE-9823
Project: Ignite
Issue Type: Task
Hi Stephan, Alexey
That's exactly what readme.io contains - installation instructions,
configuration, and examples for key-value, sql, etc. for thin clients. For
example, see these documentation pages for Node.js (currently hidden in the
latest version of the doc) :
https://apacheignite.readme.io
> You know, I'm confused with all this documentation stuff...
> For nodejs client all docs were moved from the repo to readme.io but the
> readme.md keeps the installation instructions (duplicated with
> readme.io). Probably, that's ok.
> Will add similar short readme.md to the PHP PR.
Its goo
But now in PR we have no readme at all
Agree with examples on readme.io, but other information (how to install, how
to configurate, install from sources, basic description) may be in sources,
it help a lot
Or it also should be on readme.io?
This question because in other platforms have readme exi
> 1. Because finally the docs should not be in the repo (unfortunately) but
> on readme.io.
> There is a task for that:
> https://issues.apache.org/jira/browse/IGNITE-9523
> Added the link in the jira.
Ok
> 2. Examples in readme.md are more like code snippets (mostly not big)
> intended to he
Hi Stepan,
1. Why exists second branches with all documentation? I mean they looks good
together, why need to separate?
Because finally the docs should not be in the repo (unfortunately) but
on readme.io.
There is a task for that: https://issues.apache.org/jira/browse/IGNITE-9523
Also, one
Sorry for interruption but im also review this feature and have couple
questions about documentation
1. Why exists second branches with all documentation? I mean they looks good
together, why need to separate?
Also, one place when i found this branch it is this thread, not in jira, not
in a github
gt; /home/isapego/work/ignite/modules/platforms/php/src/Apache/Ignite/Client.php(61):
> >>>>
> >>
> Apache\Ignite\Internal\Connection\ClientFailoverSocket->connect(Object(Apache\Ignite\ClientConfiguration))
> >>>> #6
> >>>>
>
Search "cpp" or "dotnet" for example.
Best Regards,
Igor
On Tue, Sep 4, 2018 at 3:21 PM Igor Sapego wrote:
Great,
I'll take a look
Best Regards,
Igor
On Wed, Aug 29, 2018 at 10:37 PM Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:
Hi folks,
stResult))
> >> #10
> >>
> /home/isapego/work/ignite/modules/platforms/php/vendor/phpunit/phpunit/src/TextUI/TestRunner.php(587):
> >> PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
> >> #11
> >>
> /home/isapego/work/ignite/m
need to edit
ignite/assembly/release-fabric-base.xml file and add appropriate
"copy" commands.
Search "cpp" or "dotnet" for example.
Best Regards,
Igor
On Tue, Sep 4, 2018 at 3:21 PM Igor Sapego wrote:
Great,
I'll take a look
Best Regards,
Igor
Prachi Garg created IGNITE-9523:
---
Summary: Document PHP thin client
Key: IGNITE-9523
URL: https://issues.apache.org/jira/browse/IGNITE-9523
Project: Ignite
Issue Type: Task
):
> PHPUnit\TextUI\Command::main()
> #14 {main}
> Am I doing something wrong?
>
> 5. When "maven package" command is executed on Ignite, no php directory
> appears
> in target/release-package-fabric/platforms directory. You need to edit
> ignite/assembly/re
"cpp" or "dotnet" for example.
Best Regards,
Igor
On Tue, Sep 4, 2018 at 3:21 PM Igor Sapego wrote:
> Great,
>
> I'll take a look
>
> Best Regards,
> Igor
>
>
> On Wed, Aug 29, 2018 at 10:37 PM Alexey Kosenchuk <
> alexey.kosenc...@nobi
Great,
I'll take a look
Best Regards,
Igor
On Wed, Aug 29, 2018 at 10:37 PM Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:
> Hi folks,
>
> PHP thin client is ready for review.
>
> Jira with the scope of work - [1].
>
> Implementation, examples, tests
Hi folks,
PHP thin client is ready for review.
Jira with the scope of work - [1].
Implementation, examples, tests:
PR - [2],
repository - [3].
API spec - [4].
Readme (how to for the client, instructions for the examples and tests,
etc.) - [5].
Regards,
-Alexey
[1] https
GitHub user ekaterina-nbl opened a pull request:
https://github.com/apache/ignite/pull/4649
IGNITE-7783 PHP Thin Client
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nobitlost/ignite ignite-7783
Alternatively you can review
30 matches
Mail list logo
