Update package descriptor after resource descriptor has been updated
See original GitHub issueHey,
I want to automatically update resource descriptors, however, the descriptor of the whole package is not updated after I update the resource descriptor.
For example:
p = Package('datapackage.json')
r = p.get_resource('r1')
r.descriptor = new_descriptor
r.commit()
p.commit()
r.descriptor # -> updated description
p.descriptor # -> still the old one
Is there a way to make code like above work?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Package Descriptor - IOx - Document
Sections and Subsections PaaS LXC Docker VM Constraints Type Minimum Schema V...
** app ** M M M M N/A Object 1.0
app ‑> cpuarch...
Read more >B weblogic.xml Deployment Descriptor Elements
This parameter identifies how often WebLogic Server checks whether a resource has been modified and if so, it reloads it. The value -1...
Read more >Maven: Failed to read artifact descriptor - java
After some time when I finishedd my coding I needed to create a JAR of my module a2. I ran "package" on a2's...
Read more >Refreshing a REST API Descriptor
Removes RAD elements that correspond to elements that have been removed from the updated Swagger document. Note: In Designer, the option to refresh...
Read more >REST Resource: projects.metricDescriptors
Once a metric descriptor is created, deleting or altering it stops data collection and ... value to zero and sets a new start...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Upon some investigation, the field/table issue is a bit different than the resource/package issue, so I’ve created a new issue over in the
tableschema-py
repository:https://github.com/frictionlessdata/tableschema-py/issues/217
It’s been fixed in Frictionless Framework as the whole working with metadata design was re-worked