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

[ bug ]慢查日志统计与明细页面导出的SQL语句不完整 #485

Closed
yuandajn578 opened this issue Oct 21, 2019 · 10 comments
Closed

Comments

@yuandajn578
Copy link
Contributor

yuandajn578 commented Oct 21, 2019

期待结果和实际结果

期待结果:
导出完整的SQL语句
实际结果:
统计页面导出结果:
image

明细页面导出结果:
image

版本信息

应用版本/分支 v1.7.0/master:

部署方式:Docker

@yuandajn578
Copy link
Contributor Author

@LeoQuote @hhyo
两位大神,这个BUG与会话管理页面无法导出完整info内容,是一个类型的。
受累了。

@yuandajn578 yuandajn578 changed the title [ bug ]慢查日志页面导出的SQL语句不完整 [ bug ]慢查日志统计与明细页面导出的SQL语句不完整 Oct 21, 2019
@hhyo
Copy link
Owner

hhyo commented Oct 21, 2019

不知道你是否愿意尝试贡献代码?上个issue中修改代码的commit记录应该很明确,大致看下应该就知道如何修改

感谢你提出的各类建议,如果能参与贡献最好不过

@yuandajn578
Copy link
Contributor Author

我是DBA,对开发不太熟悉,我先看看上个issue中修改代码的commit记录吧,争取尽快熟悉咱们的代码,最终可能还是需要大神们修复。

@yuandajn578
Copy link
Contributor Author

@hhyo
我参考上个issue中修改代码的commit记录,修改了本地的对应文件,然后重启了archery容器,但是会话管理页面导出的结果中未包含完整Info列,是不是我的修改有误呢?
image

@LeoQuote
Copy link
Collaborator

如果是用docker的话是需要重新从源码build 镜像的.

@hhyo
Copy link
Owner

hhyo commented Oct 21, 2019

image

先选择再导出

@yuandajn578
Copy link
Contributor Author

好的,我正在从重新从源码build 镜像,多谢多谢。

@hhyo hhyo closed this as completed in 4a09cb1 Oct 21, 2019
@yuandajn578
Copy link
Contributor Author

如果是用docker的话是需要重新从源码build 镜像的.

大神,我本地修改HTML源码之后,尝试重新从本地的源码build 镜像,一直没成功,还请大神不吝赐教具体的build镜像步骤。多谢了。

@hhyo
Copy link
Owner

hhyo commented Oct 22, 2019

@yuandajn578 目前没有将基础镜像独立出来,由于集成组件多,在线build会很慢,国内网络不好还会超时

如果没有依赖变更的话,可以将镜像内的工程目录映射到本地,具体操作可以自行检索

@yuandajn578
Copy link
Contributor Author

yuandajn578 commented Oct 22, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants