aerospike / php-client

Aerospike Client for PHP 8
https://aerospike.github.io/php-client/
9 stars 2 forks source link

Can not delete a key after upgrading to version 1.0 #27

Closed mpPassendo closed 6 months ago

mpPassendo commented 7 months ago

Hi,

I just updated from v0.4.0-alpha to version 1.0. I tried to run my previous test but I got an error "attempt to use an Enterprise feature on a Community server or a server without the applicable feature key". It turns out that that exception is thrown if I call delete method. I tried with examples you provided - and I can confirm it that it is not working and I am getting that error. I am using this image as server aerospike/aerospike-server:6.3.0.16_1. In the example you provided you are also using method close on client and that method is removed with latest update.

I managed to make it work upgrading my docker setup - but I needed some time. It would be nice if you provide these instructions as well.

Thanks, Milan

vmsachin commented 7 months ago

Hello,

Thank you for the feedback @mpPassendo . Just had a clarifying question - when you mention the upgrading the docker setup, what exactly was upgraded? It would help us review this in depth

Thank you!

mpPassendo commented 7 months ago

Hi,

I mean upgrading my docker development environment (upgraded Dockerfile to use PHP 8.3 instead of 8.1 that v0.4.0-alpha supported). So I created new aerospike.so file for PHP 8.3 and I am running socket using aerospike-connection-manager whenever docker container is up (using entrypoint). Do you need more info?

Regards, Milan

vmsachin commented 7 months ago

Hi Milan,

Im trying to understand what caused the failure. Was it because you were using an older version of the Aerospike-connection-manager?

mpPassendo commented 7 months ago

Hi,

Nope. Let me simplify it :) I completed all steps, I can see that Aerospike extension is loaded and that is working. I can set a key but I can not delete it. When I tried to delete it - I got this message "attempt to use an Enterprise feature on a Community server or a server without the applicable feature key". Before updating everything worked. Please let me know if you need more information.

Thanks Milan

vmsachin commented 7 months ago

Thank you for simplifying it :D. I am trying to replicate the issue but unable to do so. I am using php-client 1.0.0 and Aerospike server 6.3.0.6_1. Could you try to upgrade the server v7.0 and see if you get the same issue.

mpPassendo commented 7 months ago

Hi,

I upgraded Aerospike server to v7.0, php version 8.3.4 - but I got the same error unfortunately - "Aerospike\AerospikeException: attempt to use an Enterprise feature on a Community server or a server without the applicable feature key". All the other operations work perfectly.

mpPassendo commented 7 months ago

Hi,

I tried to create simplified docker setup for php project & Aerospike - https://github.com/pssndo/astesting

When I tried to run index.php I got the same message "Aerospike\AerospikeException: attempt to use an Enterprise feature on a Community server or a server without the applicable feature key". Set & get is working as expected.

Thanks Milan

piyush-bansal1989 commented 7 months ago

@vmsachin : We also getting the same issue [25] attempt to use an Enterprise feature on a Community server or a server without the applicable feature key. Is there any specific configuration required for community edition? or do we need to upgrade the aerospike server version? because the same issue we haven't encountered with previous client versions (PHP 7.x).

vmsachin commented 7 months ago

@mpPassendo Thank you for the GitHub repo. I reproduced the issue. Seems like it happening with the community edition of Aerospike Server. We are looking why this is happening. Will update once it is fixed. cc: @piyush-bansal1989

Thanks!

vmsachin commented 7 months ago

@mpPassendo @piyush-bansal1989 we have identified the issue, will release the fix in patch 1.0.1 will notify you on release

vmsachin commented 6 months ago

@mpPassendo @piyush-bansal1989 This issue has been fixed with v1.0.1 release. Please let us know if you face any other issues.