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.

Sign up for GitHub

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

Jump to bottom

Exporting message search results #597

Open
sreenivasvp opened this issue Jun 28, 2021 · 11 comments · May be fixed by #4323
Open

Exporting message search results #597

sreenivasvp opened this issue Jun 28, 2021 · 11 comments · May be fixed by #4323
Labels
scope/frontend status/accepted An issue which has passed triage and has been accepted type/feature A new feature
Projects
Roadmap

Comments

@sreenivasvp
Copy link

Is your proposal related to a problem?

(Write your answer here.)
Currently, we can save only selected message, it is good to have a feature to download all, searched result messages

Describe the solution you'd like

(Describe your proposed solution here.)

Describe alternatives you've considered

(Write your answer here.)

Additional context

(Write your answer here.)
@sreenivasvp sreenivasvp added the type/enhancement En enhancement to an already existing feature label Jun 28, 2021
@germanosin
Copy link
Contributor

Hi, @sreenivasvp. Thank you for creating this issue. What format do you expect it to be?

@germanosin germanosin added this to the 0.3 milestone Jun 28, 2021
@sreenivasvp
Copy link
Author

Hi @germanosin
I would personally feel we dump message as is, In our case we store and retrieve a json message.

@germanosin germanosin modified the milestones: 0.3, 0.4 Sep 16, 2021
@Haarolean Haarolean added this to 0.4 in Roadmap Oct 25, 2021
@Haarolean Haarolean changed the title Support for downloading all, searched result messages Exporting message search results Oct 25, 2021
@Haarolean Haarolean added scope/backend status/accepted An issue which has passed triage and has been accepted labels Oct 25, 2021
@Haarolean Haarolean moved this from 0.4 to 0.5 in Roadmap Oct 25, 2021
@Haarolean Haarolean modified the milestones: 0.4, 0.5 Oct 29, 2021
@Haarolean Haarolean added type/feature A new feature and removed type/enhancement En enhancement to an already existing feature labels Dec 21, 2021
@Haarolean Haarolean added this to Features in Release 0.5 Apr 21, 2022
@Haarolean Haarolean added the status/needs-attention Collective discussion is required label May 4, 2022
@Haarolean Haarolean moved this from 0.5 to 0.6 in Roadmap May 31, 2022
@Haarolean Haarolean moved this from 0.6 to 0.7 in Roadmap May 31, 2022
@Haarolean Haarolean modified the milestones: 0.5, 0.7 May 31, 2022
@Haarolean Haarolean removed this from Features in Release 0.5 May 31, 2022
@Haarolean Haarolean removed this from the 0.7 milestone Jun 8, 2022
@sw-tracker
Copy link

I would suggest adding an environment variable to enable/disable this feature. In some industries with sensitive data, we will not be allowed to export data so easily.

@Haarolean
Copy link
Contributor

I would suggest adding an environment variable to enable/disable this feature. In some industries with sensitive data, we will not be allowed to export data so easily.

#1352

@sw-tracker
Copy link

I would suggest adding an environment variable to enable/disable this feature. In some industries with sensitive data, we will not be allowed to export data so easily.

#1352

While I think data-masking is awesome and a must-have feature, I would still add an env variable to enable/disable export. A mistake in masking customer sensitive data, and it being exportable is the nightmare of our security team. It is actually one of the reasons we are not using kowl...

@wanisfahmyDE
Copy link
Contributor

Hi there,

is there any plans to have this feature soon?

Thanks

@Haarolean
Copy link
Contributor

Hi there,

is there any plans to have this feature soon?

Thanks

Hey, not unless we get some external contributors willing to do this now. We have other features prioritised right now. Stay tuned!

@Haarolean Haarolean moved this from 0.8 to 0.9 in Roadmap Dec 15, 2022
@metathrone
Copy link

metathrone commented Dec 27, 2022 •
edited

hoping for this useful feature

@tsyma
Copy link

tsyma commented Jan 5, 2023

I feel like this feature will be very helpful. We are forced to use "pagination" and save results to one file manually. It's really boring. Please consider possibility to implement this feature.

@Haarolean Haarolean moved this from 0.9 to 0.7 in Roadmap Jan 17, 2023
@Haarolean Haarolean removed the status/needs-attention Collective discussion is required label Jan 17, 2023
@wanisfahmyDE
Copy link
Contributor

it would be also really helpful if the messages are exported in json files. currently it seems that it's only possible to have it only in txt format with the char escape markers. After some search, I guess this part to be the culprit: https://github.com/provectus/kafka-ui/blob/master/kafka-ui-react-app/src/lib/hooks/useDataSaver.ts#L19-L26

@Haarolean Haarolean moved this from 0.7 to 0.8 in Roadmap Mar 9, 2023
@Haarolean Haarolean moved this from 0.8 to 0.9 in Roadmap Apr 26, 2023
@jcpunk
Copy link

jcpunk commented Jul 6, 2023

I'll confess interest in this feature

@Haarolean Haarolean mentioned this issue Aug 25, 2023
Closed
2 tasks
@cacapouh cacapouh linked a pull request Nov 12, 2023 that will close this issue
Draft
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
scope/frontend status/accepted An issue which has passed triage and has been accepted type/feature A new feature
Projects
Roadmap
0.9
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

FE,BE: Add download button cacapouh/kafka-ui
8 participants
@germanosin @Haarolean @sreenivasvp @jcpunk @tsyma @metathrone @sw-tracker @wanisfahmyDE