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

Export issue with large volume volume of entities #5798

Closed
NiQuintin opened this issue Feb 2, 2024 · 6 comments
Closed

Export issue with large volume volume of entities #5798

NiQuintin opened this issue Feb 2, 2024 · 6 comments
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@NiQuintin
Copy link

NiQuintin commented Feb 2, 2024

Description

When creating a report containing many entities (+300) with relationships between them, and performing a full json export of the report, not all entities are exported.

Environment

OpenCTI version: 5.12.29

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a report with many entities in platform A and many relationships,
  2. Make a full json export (normally at this stage all entities may not be exported)

Expected Output

A complete export with no missing entities.

Actual Output

Not all entities are exported.

Additional information

Is this a bug or a deliberate limitation?

Note: When ingested into another instance (both instances are of the same version) after workbensh validation, many 'name': 'MISSING_REFERENCE_ERROR', 'message': 'Element(s) not found' errors appear.

@NiQuintin NiQuintin added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 2, 2024
@richard-julien
Copy link
Member

Looks like more an export problem than an import one.

@NiQuintin NiQuintin changed the title MISSING_REFERENCE_ERROR when ingesting a large volume of entities Export issue with large volume volume of entities Feb 2, 2024
@NiQuintin
Copy link
Author

You're right, i've modified the description.

@richard-julien
Copy link
Member

Im not able to reproduce for now. Can you pinpoint a specific report for the export and maybe thats missing exactly in it?
Thanks

@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 5, 2024
@NiQuintin
Copy link
Author

@SamuelHassine SamuelHassine added this to the Release 6.0.0 milestone Feb 5, 2024
@Jipegien
Copy link
Member

@NiQuintin Can you test on testing to see if you reproduce it? It might be solved already.

@Jipegien Jipegien added the needs more info Intel needed about the use case label Feb 16, 2024
@NiQuintin
Copy link
Author

NiQuintin commented Feb 16, 2024

It works on testing @Jipegien

@Jipegien Jipegien added solved use to identify issue that has been solved (must be linked to the solving PR) and removed needs more info Intel needed about the use case labels Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

5 participants