Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnsupportedOperationException when using pipeline and execute #3112

Closed
J4ckTh3R1pper opened this issue Feb 28, 2025 · 3 comments
Closed

UnsupportedOperationException when using pipeline and execute #3112

J4ckTh3R1pper opened this issue Feb 28, 2025 · 3 comments
Labels
status: duplicate A duplicate of another issue

Comments

@J4ckTh3R1pper
Copy link

J4ckTh3R1pper commented Feb 28, 2025

spring-data-redis version: 3.4.3
I got following error when trying to execute a HEXPIREAT command in pipelined execution, which is kinda similar to redis/lettuce#2831 (comment)

Caused by: java.lang.UnsupportedOperationException: io.lettuce.core.output.ByteArrayOutput does not support set(long)
	at io.lettuce.core.output.CommandOutput.set(CommandOutput.java:111)
	at io.lettuce.core.protocol.RedisStateMachine.safeSet(RedisStateMachine.java:782)
	at io.lettuce.core.protocol.RedisStateMachine.handleInteger(RedisStateMachine.java:433)
	at io.lettuce.core.protocol.RedisStateMachine$State$Type.handle(RedisStateMachine.java:210)
	at io.lettuce.core.protocol.RedisStateMachine.doDecode(RedisStateMachine.java:363)
	at io.lettuce.core.protocol.RedisStateMachine.decode(RedisStateMachine.java:324)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:844)
	at io.lettuce.core.protocol.CommandHandler.decode0(CommandHandler.java:795)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:778)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:661)
	at io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:601)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1357)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:868)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:796)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:732)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:658)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:833)


@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 28, 2025
@mp911de
Copy link
Member

mp911de commented Mar 3, 2025

If you would like us to spend some time helping you to diagnose the problem, please spend some time describing it and, ideally, providing a minimal yet complete sample that reproduces the problem.
You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

Also, I do not see any Spring-related code nor stack traces which makes me question whether this is the right place to report the issue.

@mp911de mp911de added the status: waiting-for-feedback We need additional information before we can continue label Mar 3, 2025
@J4ckTh3R1pper
Copy link
Author

Here's my example code:

demo3112.tar.gz

redis version is 7.4.2

@spring-projects-issues spring-projects-issues added status: feedback-provided Feedback has been provided and removed status: waiting-for-feedback We need additional information before we can continue labels Mar 3, 2025
@mp911de
Copy link
Member

mp911de commented Mar 3, 2025

Using Hash Field expiry is not yet supported, see #3054.

@mp911de mp911de closed this as completed Mar 3, 2025
@mp911de mp911de added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged status: feedback-provided Feedback has been provided labels Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants