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

Get info from stream without materializing #163

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 6 comments
Open

Get info from stream without materializing #163

GoogleCodeExporter opened this issue Mar 24, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

from the thread "New release of FuelMooseExtension"

        Is there a way to list all required classes before performing an actual load ? 


    Not right now, but we could add it if desired. We already talked about Martin about that. The idea was to kind of "simulate" the materialization (reading the stream) and get an object with information. So that you can ask for example, the needed classes.


Now Martin pointed me out the previous discussion we had about it. Basically, 
it consist of something like this:

info := FLMaterializer newDefault infoFrom: stream.
info globalClasses --> {Point. Zaraza. Etc.}
info internalClasses ---> {}
info objectCount ---> 32000
info clusterCount ---> 5
info fuelVersion  ->  15
info allGlobals -> {Transcript.  ... ]

etc...

Original issue reported on code.google.com by marianopeck on 31 May 2012 at 8:32

@stale
Copy link

stale bot commented May 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label May 18, 2021
@theseion
Copy link
Owner

This would also be nice for tooling (e.g. GTInspector) that can easily display meta information. Not a priority though.

@stale stale bot removed the stale label Oct 30, 2021
@stale
Copy link

stale bot commented Dec 29, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label Dec 29, 2021
@theseion
Copy link
Owner

theseion commented Jan 2, 2022

Not stale.

@stale stale bot removed the stale label Jan 2, 2022
@stale
Copy link

stale bot commented Mar 3, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label Mar 3, 2022
@theseion
Copy link
Owner

theseion commented Mar 4, 2022

Not stale

@theseion theseion added the pinned Never mark this issue stale label Mar 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants