-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error while trying to output a large dataset in VSCode w/ ECL Extension #349
Comments
You are hitting the limit of outputting a large dataset "inside" the WU. If you output it to a logical file instead it will work. |
Can you kindly provide the syntax on how to output to a logical file.
Is it the same syntax as OUTPUT WORKUNIT FILES mentioned in the ECL
Language Reference?
Also, will I be able to use the contents of the logical file in Observable
HQ?
…On Thu, Jul 20, 2023 at 8:07 PM Gordon Smith ***@***.***> wrote:
You are hitting the limit of outputting a large dataset "inside" the WU.
If you output it to a logical file instead it will work.
—
Reply to this email directly, view it on GitHub
<#349 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3OYA7STLPETQ4YMCB5GY4DXRE66LANCNFSM6AAAAAA2Q652ZY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
layout:=RECORD input:=DATASET('~hthor::in:person_name',layout,thor); step1:=OUTPUT(input,,'~hthor::in:different_name',thor,compressed); // How you write a logical file. dsOut:=DATASET('~hthor::in:different_name',layout,thor); step2:=OUTPUT(dsOut,named('RESULTS'));// How you output the results ORDERED(step1,step2); |
I was able to write the dataset to a logical file. I want to further use
these contents in an Observable Javascript cell. Is there any way to access
it?
…On Thu, Jul 20, 2023 at 8:49 PM Maurice Vigueras ***@***.***> wrote:
layout:=RECORD
string first_name;
string middle_name;
string last_name;
END;
input:=DATASET('~hthor::in:person_name',layout,thor);
step1:=OUTPUT(input,,'~hthor::in:different_name',thor,compressed); // How
you write a logical file.
dsOut:=DATASET('~hthor::in:different_name',layout,thor);
step2:=OUTPUT(dsOut,named('RESULTS'));// How you output the results
ORDERED(step1,step2);
—
Reply to this email directly, view it on GitHub
<#349 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3OYA7UQHJRNHZV444CNRGTXRFD7FANCNFSM6AAAAAA2Q652ZY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Publish your query on the ecl watch and import using JSON. |
Are there any notebooks I can use for reference?
The only one I could find was
***@***.***/fetch-ecl-record-layout-from-logical-file-name
…On Thu, Jul 20, 2023 at 10:59 PM Maurice Vigueras ***@***.***> wrote:
Publish your query on the ecl watch and import using JSON.
—
Reply to this email directly, view it on GitHub
<#349 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3OYA7XGHLQTE7GFCCYOANDXRFTGLANCNFSM6AAAAAA2Q652ZY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Are you an intern at LexisNexis or working for LexisNexis in anyway? If so, send me an internal email looking up my name on teams and I can walk you thru it. |
I am part of a research project under Mr. Hugo Watanuki, under the
RVCE-LexisNexis CoE. If you can provide me with your email address, it
would be much appreciated.
Also, when you said 'Import using JSON', did you mean to download the
logical file as a JSON file and then use it in OJS?
…On Thu, Jul 20, 2023 at 11:30 PM Maurice Vigueras ***@***.***> wrote:
Are you an intern at LexisNexis or Interning in anyway? If so, send me an
internal email looking up my name on teams and I can walk you thought it.
—
Reply to this email directly, view it on GitHub
<#349 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3OYA7SSAFTRFBCKVSHHBPTXRFW5PANCNFSM6AAAAAA2Q652ZY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Found him on the system. Send me your email and I will schedule a one on one sometime soon for a walkthrough. |
You have two options: you either write embedded Python in ECL which I am not too familiar, or you export your aggregated data externally using a rest API provided within the ECL Watch itself. It requires multiple steps and therefore it would be much easier for me to just walk you through it. |
Thank you, that would be of great help.
Here is my email address:
***@***.***
Kindly note that I live in India, which may not match with your timings.
Hence it would be highly appreciated if we could find a time which is
comfortable for both of us.
Also, regarding the Python embedding, my output is a result from a Python
function itself, which I want to port to OJS. Is there any other methods of
doing so?
…On Thu, 20 Jul, 2023, 11:54 pm Maurice Vigueras, ***@***.***> wrote:
You have two options: you either write embedded Python in ECL which I am
not too familiar, or you export your aggregated data externally using a
rest API provided within the ECL Watch itself. It requires multiple steps
and therefore it would be much easier for me to just walk you through it.
—
Reply to this email directly, view it on GitHub
<#349 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3OYA7TMLUMQOPMQJUSM63LXRFZXFANCNFSM6AAAAAA2Q652ZY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Find me in teams, your email does not show up because it is encrypted for security reasons. Full name is Maurice Vigueras. |
I am not part of your teams environment, thus I cannot check you up.
I provided my email address in the previous email.
…On Fri, Jul 21, 2023 at 1:04 AM Maurice Vigueras ***@***.***> wrote:
Find me in teams, your email does not show up because it is encrypted for
security reasons. Full name is Maurice Vigueras.
—
Reply to this email directly, view it on GitHub
<#349 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3OYA7QJVARSV6RRDEZS553XRGB45ANCNFSM6AAAAAA2Q652ZY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The following error is occurring when a large dataset of 960000 records approximately is tried to be displayed in an ECL notebook.
The text was updated successfully, but these errors were encountered: