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

HPCC-30776 ECL mods to support pluggable file format syntax *** WIP *** #18107

Conversation

dcamper
Copy link
Contributor

@dcamper dcamper commented Dec 1, 2023

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

Copy link

github-actions bot commented Dec 1, 2023

@dcamper dcamper requested a review from ghalliday December 1, 2023 20:29
Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you're getting to grips with the structure. I would also add a new operator no_filetype, create that in setPluggableModeExpr
e.g.

targetAttr.setExpr(createValue(no_filetype, makeNullType(), createAttribute(fileFormat), *options));

Then search for no_csv in the sources in ecl/hql and add corresponding entries. You could also do the same for ecl/hqlcpp, but I would probably leave that to a separate PR, which meant the new syntax generated the generic disk read activity.

@@ -10529,6 +10529,75 @@ mode
$$.setExpr(createValue(no_json, makeNullType(), args));
}
| pipe
| TYPE '(' FLAT ')'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth special casing these? I was expecting these to all generate the new format, and by implication be a way of explicitly using the new generic disk read code.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am taking this change very slowly while I learn the vast array of helpers and structs. As of this writing, I was focused solely on changing the syntax and making sure it worked. Next step will be changing the underlying code and how it is called.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also: A plugin-style filetype will process options differently than flex. This is definitely not a problem with a new filetype such as Parquet, but may cause backwards-compatibility issues with an existing filetype (errors may be caught at different times and/or reported differently). Is that a concern, given that this is introducing a new syntax?

// TODO: Look for a plugin filetype of name fileFormatStr
DBGLOG("HqlGram::setPluggableModeExpr processing file type %s", fileFormatStr.str());

// Following is a placeholder to make the parser happy -- note the hardwiring
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whitespace: tabs being used for indentation rather than spaces.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

IAtom * fileFormat = lower(mode.getId());
StringBuffer fileFormatStr(fileFormat->queryStr());

// TODO: Look for a plugin filetype of name fileFormatStr
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Questionable whether it needs to check for a type at this point. Advantages and disadvantages...

@dcamper dcamper force-pushed the hpcc-30776-hql-dataset-generic-file-format branch 2 times, most recently from 8c393d8 to ea1fb6c Compare December 7, 2023 18:36
@dcamper dcamper force-pushed the hpcc-30776-hql-dataset-generic-file-format branch 2 times, most recently from 3dbb5fb to b5cd3f3 Compare December 19, 2023 14:51
@dcamper dcamper force-pushed the hpcc-30776-hql-dataset-generic-file-format branch from b5cd3f3 to 0443f49 Compare December 27, 2023 12:51
@dcamper dcamper force-pushed the hpcc-30776-hql-dataset-generic-file-format branch 3 times, most recently from ad3d760 to c4296cb Compare January 5, 2024 14:51
@dcamper dcamper force-pushed the hpcc-30776-hql-dataset-generic-file-format branch from c4296cb to 9a2c32d Compare January 11, 2024 19:22
@dcamper
Copy link
Contributor Author

dcamper commented Jan 18, 2024

Closing while continuing work. Will open a new draft later.

@dcamper dcamper closed this Jan 18, 2024
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

Successfully merging this pull request may close these issues.

2 participants