AWS数据胶水爬网桌找不到
我正在运行爬行者，在日志中，它向我展示了一个表格并添加到数据库中，该表也已创建。但是，当我想检查桌子时，它不在那里。我发现一些问题，人们由于缺乏权限而无法创建桌子，但这不是我的错误。它还在添加的轨道下方显示。值从0跳到1，但我在任何地方都找不到表。 也许有人有类似的问题？
下面您可以看到日志，这些日志表明应添加
，
但是如果我转到表格部分，则会显示两个表格，我在其他crawler之前创建了这些表。我将新的p设置为两个之前，这次我没有得到任何桌子
更新：
可以是UI错误吗？当我在CLI中运行桌子时，我可以看到表。既然我对使用CLI的工作不太熟悉，我想在Der UI上完成它？我可以做什么可以拆除UI
I am running my crawler and in logs it shows me that a table has be created and added to the database which also has been created. However when I want to check the table it's not there. I found some problems where people couldn't create a table because of lacking permissions, but that shouldn't be the mistake in my case. It also shows in the crawler under table added. Value jumps from 0 to 1 but I can't find the table anywhere.
Maybe someone had a similar problem ?
below you can see the logs which show that it should be added
but if i go to the tables section it shows two tables which i createdd before with another crawler. i set the new one p as the two before still this time i'm not getting any table
UPDATE:
Can it be a UI bug ? when I'm running get tables in CLI i can see the table. Since I'm not very familiar with working with CLI I wanted to finish it over der UI? Is there anthing I can do to unbug the UI
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
实际上，在我的情况下重新启动浏览器（Chrome）有帮助。当我试图在AWS控制台中看到桌子时，它告诉我它不存在。同时，我看到它在AWS胶水表列表中列出，并能够选择它并编辑其架构。
我认为还有另一个UI错误。由于模式问题，它不允许我通过雅典娜查询桌子。问题是我已经固定了，模式是正确的。我花了大约5个小时的时间来使用轨道/表格/模式配置，但是我要做的就是关闭雅典娜UI中的所有查询选项卡，我试图查询这张桌子，只保留单个桌子。它炸毁了我的想法。
Actually, restarting a browser (Chrome) in my case helped. When I tried to see the table in AWS Console it told me that it doesn't exist. At the same time I saw it listed in AWS Glue tables list and was able to select it and edit its schema.
There was another UI bug I think. It didn't allow me to query my table via Athena because of schema issues. The problem was that I have it already fixed and schema was correct. I spent ~5 hours playing with crawler/table/schema configurations but all I needed to do was to close all query tabs in Athena UI where I tried to query this table and keep only single one. It blew up my mind....