密钥未加载:密钥< Frame>.通过H2O API调用中的ParseSetup发布源帧时 [英] Key not loaded: Key<Frame> while POSTing source frame through ParseSetup in H2O API call

问题描述

我的代码:

curl -X POST http://localhost:54321/3/ParseSetup --data 'source_frames=["/root/documents/my_file.csv"]'

错误:

java.lang.IllegalArgumentException:密钥未加载:密钥位于water.api.ParseSetupHandler.guessSetup(ParseSetupHandler.java:31)

java.lang.IllegalArgumentException: Key not loaded: Key at water.api.ParseSetupHandler.guessSetup(ParseSetupHandler.java:31)

帮助:

有人可以帮助解决这个问题吗?我是否缺少任何参数?

Could anyone help to resolve this? Am I missing any parameter?

使用的H2O版本: h2o-3.10.0.10

推荐答案

我的建议是打开Flow( http://localhost:54321 )，然后启动Firebug(或所选浏览器中的同等功能)和网络"标签.然后从Flow导入文件，然后进行解析，并记下发送的确切内容.

My suggestion is to open Flow (http://localhost:54321) in a browser, then start Firebug (or the equivalent in your browser of choice), and the network tab. Then do a file import from Flow, then the parse, and make a note of exactly what it is sending.

(或者从R或Python导入数据包嗅探器，但这听起来更困难.)

(Alternatively do the import from R or Python with a packet sniffer going, but that sounds like harder work.)

您先执行/3/ImportFiles调用吗?(我实际上看到了三个调用:ImportFiles，ParseSetup，Parse.)

Did you do the /3/ImportFiles calls first? (I actually see three calls: ImportFiles, ParseSetup, Parse.)

在我的快速测试中，我在所有路径上都看到了"nfs://"前缀.不知道这是否重要.

In my quick test I'm seeing the "nfs://" prefix on all the paths. Don't know if that is important.

但是，我的第一个猜测是您应该使用-data-urlencode 而不是-data .或手动对数据进行URL编码.

But, my first guess would be that you should be using --data-urlencode instead of --data. Or manually URL-encode your data.

这篇关于密钥未加载:密钥< Frame>.通过H2O API调用中的ParseSetup发布源帧时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！